[Freeipa-users] WebUI authentication problems

I just installed a new server on Fedora 21 Server, using the rolekit deployment
tool. Everything was installed and configured (I hope) properly, but I'm
running into a problem. The version is freeipa-server-4.1.2-1.fc21.x86_64, and
I can connect to the WebUI only after a restart of ipa.service.
After approximately 15 minutes, I am kicked out of the active session - while
in the middle of using it - and cannot log back in. Login was attempted from 4
browsers across two machines, and every time the login screen returns with
"Your session has expired. Please re-login."
[Fri Feb 20 00:37:03.972736 2015] [auth_kerb:error] [pid 1158] [client
10.1.0.15:54958] gss_accept_sec_context() failed: Unspecified GSS failure.
Minor code may provide more information (, ASN.1 structure is missing a
required field), referer: https://vader.dom.net/ipa/ui/index.html
[Fri Feb 20 00:37:34.300510 2015] [auth_kerb:error] [pid 1173] [client
10.1.0.15:54961] gss_accept_sec_context() failed: Unspecified GSS failure.
Minor code may provide more information (, ASN.1 structure is missing a
required field), referer: https://vader.dom.net/ipa/ui/index.html
[Fri Feb 20 00:37:34.406615 2015] [auth_kerb:error] [pid 1616] [client
10.1.0.15:54965] gss_accept_sec_context() failed: Unspecified GSS failure.
Minor code may provide more information (, ASN.1 structure is missing a
required field), referer: https://vader.dom.net/ipa/ui/index.html
[Fri Feb 20 00:37:50.356014 2015] [auth_kerb:error] [pid 1161] [client
10.1.0.15:54966] gss_accept_sec_context() failed: Unspecified GSS failure.
Minor code may provide more information (, ASN.1 structure is missing a
required field), referer: https://vader.dom.net/ipa/ui/index.html
[Fri Feb 20 00:37:52.263088 2015] [auth_kerb:error] [pid 1417] [client
10.1.0.15:54968] gss_accept_sec_context() failed: Unspecified GSS failure.
Minor code may provide more information (, ASN.1 structure is missing a
required field), referer: https://vader.dom.net/ipa/ui/index.html
[Fri Feb 20 00:37:52.327075 2015] [auth_kerb:error] [pid 1168] [client
10.1.0.15:54967] gss_accept_sec_context() failed: Unspecified GSS failure.
Minor code may provide more information (, ASN.1 structure is missing a
required field), referer: https://vader.dom.net/ipa/ui/index.html
[Fri Feb 20 00:45:35.603016 2015] [auth_kerb:error] [pid 1173] [client
10.1.1.17:54157] gss_accept_sec_context() failed: An unsupported mechanism was
requested (, Unknown error), referer: https://vader.dom.net/ipa/ui/
Restarting httpd, I can log in, and am immediately logged out again with the
above errors.
Restarting ipa.service, I was able to log in with my user account, and was
notified that my password expires in 0 days - even though it was just created
less than an hour ago.
Is this a known issue, or is there a hidden problem with the rolekit deployment
that I need to track down?

CCing Petr for Web UI and Simo for the Kerberos part. We know about several
common gotchas related to Web UI auth, having them documented on
http://www.freeipa.org/page/Troubleshooting#Cannot_authenticate_to_Web_UI

But this seems as a new case. You can still check the pointers on this page
though. If none of them help, it may help to show us:

- the Kerberos ticket and default encryptions:
$ kinit
$ klist -e

- any related Kerberos errors from /var/log/krb5kdc.log

Martin

--
Manage your subscription for the Freeipa-users mailing list:
https://www.redhat.com/mailman/listinfo/freeipa-users
Go To http://freeipa.org for more info on the project

Petr Vobornik

2015-02-20 09:53:28 UTC

Default FreeIPA session lifetime is 20mins. Expiration time is extended
on each request. Session also expires when krb ticket expires. We have
known issue that Web UI, if SSO is used, does not work if ticket expires
in 5mins but it produces little bit different output.

Login was
attempted from 4
browsers across two machines, and every time the login screen returns with
"Your session has expired. Please re-login."

Does it work if you use forms-based authentication or if you use CLI tool?

[Fri Feb 20 00:37:03.972736 2015] [auth_kerb:error] [pid 1158] [client
10.1.0.15:54958] gss_accept_sec_context() failed: Unspecified GSS failure.
Minor code may provide more information (, ASN.1 structure is missing a
required field), referer: https://vader.dom.net/ipa/ui/index.html
[Fri Feb 20 00:37:34.300510 2015] [auth_kerb:error] [pid 1173] [client
10.1.0.15:54961] gss_accept_sec_context() failed: Unspecified GSS failure.
Minor code may provide more information (, ASN.1 structure is missing a
required field), referer: https://vader.dom.net/ipa/ui/index.html
[Fri Feb 20 00:37:34.406615 2015] [auth_kerb:error] [pid 1616] [client
10.1.0.15:54965] gss_accept_sec_context() failed: Unspecified GSS failure.
Minor code may provide more information (, ASN.1 structure is missing a
required field), referer: https://vader.dom.net/ipa/ui/index.html
[Fri Feb 20 00:37:50.356014 2015] [auth_kerb:error] [pid 1161] [client
10.1.0.15:54966] gss_accept_sec_context() failed: Unspecified GSS failure.
Minor code may provide more information (, ASN.1 structure is missing a
required field), referer: https://vader.dom.net/ipa/ui/index.html
[Fri Feb 20 00:37:52.263088 2015] [auth_kerb:error] [pid 1417] [client
10.1.0.15:54968] gss_accept_sec_context() failed: Unspecified GSS failure.
Minor code may provide more information (, ASN.1 structure is missing a
required field), referer: https://vader.dom.net/ipa/ui/index.html
[Fri Feb 20 00:37:52.327075 2015] [auth_kerb:error] [pid 1168] [client
10.1.0.15:54967] gss_accept_sec_context() failed: Unspecified GSS failure.
Minor code may provide more information (, ASN.1 structure is missing a
required field), referer: https://vader.dom.net/ipa/ui/index.html
[Fri Feb 20 00:45:35.603016 2015] [auth_kerb:error] [pid 1173] [client
10.1.1.17:54157] gss_accept_sec_context() failed: An unsupported mechanism was
requested (, Unknown error), referer: https://vader.dom.net/ipa/ui/

This looks like a culprit to me, though IDK what's its cause. Simo may
know more.

In a meantime you could try to enable debugging to get more info from
/var/log/httpd/error_log by creating /etc/ipa/server.conf and restarting
httpd.

# cat /etc/ipa/server.conf
[global]
debug=True

You could also open browser develeper tools (press F12) and inspect XHR
communication in network tab [1]. Check especially if some request to
/ipa/session/json or ipa/session/login_kerberos or
ipa/session/login_password does not end with 401 Unauthorized status
code. And then what's the cause of next 401 after series of 200. It
might contain some pointers. Like session expiration time and such.

[1] Loading Image...

Restarting httpd, I can log in, and am immediately logged out again with the
above errors.
Restarting ipa.service, I was able to log in with my user account, and was
notified that my password expires in 0 days - even though it was just created
less than an hour ago.

Have you modified Kerberos Ticket Policy or any Password Policy?

Is this a known issue, or is there a hidden problem with the rolekit deployment
that I need to track down?

It's not a known issue.

Post by Martin Kosek
CCing Petr for Web UI and Simo for the Kerberos part. We know about
several common gotchas related to Web UI auth, having them documented on
http://www.freeipa.org/page/Troubleshooting#Cannot_authenticate_to_Web_UI
But this seems as a new case. You can still check the pointers on this
$ kinit
$ klist -e
- any related Kerberos errors from /var/log/krb5kdc.log
Martin

--
Petr Vobornik
--
Manage your subscription for the Freeipa-users mailing list:
https://www.redhat.com/mailman/listinfo/freeipa-users
Go To http://freeipa.org for more info on the project

Gianluca Cecchi

2015-02-20 10:44:41 UTC

Hello
I actually have quite similar problems in CentOS 7 too,
with ipa-server-3.3.3-28.0.1.el7.centos.3.x86_64 and related packages
SO the same behavior that if I restart ipa service I'm able to connect
(thanks btw, I didn't realize that, having big problems using the WebUI)
and that my errors are of this type

[Fri Feb 20 10:32:15.850834 2015] [auth_kerb:error] [pid 2029] [client
192.168.1.128:50147] gss_accept_sec_context() failed: An unsupported
mechanism was requested (, Unknown error), referer:
https://c7server.localdomain.local/ipa/ui/
[Fri Feb 20 10:32:22.670791 2015] [auth_kerb:error] [pid 15793] [client
192.168.1.128:50150] krb5_get_init_creds_password() failed: Decrypt
integrity check failed, referer: https://c7server.localdomain.local/ipa/ui/

This happens both from an external browser (I enabled form authentication)
and from a firefox session launched from the ipa server itself after
configuring it for kerberos.

I don't want to mess with this thread so let me know if I have to open a
dedicated thread specifying for example CentOS 7 or you think it is ok to
get in here... so that I paste here other relevant info.

Thanks in advance

Gianluca

Simo Sorce

2015-02-20 14:04:23 UTC

Post by Gianluca Cecchi

Hello
I actually have quite similar problems in CentOS 7 too,
with ipa-server-3.3.3-28.0.1.el7.centos.3.x86_64 and related packages
SO the same behavior that if I restart ipa service I'm able to connect
(thanks btw, I didn't realize that, having big problems using the WebUI)
and that my errors are of this type
[Fri Feb 20 10:32:15.850834 2015] [auth_kerb:error] [pid 2029] [client
192.168.1.128:50147] gss_accept_sec_context() failed: An unsupported
https://c7server.localdomain.local/ipa/ui/
[Fri Feb 20 10:32:22.670791 2015] [auth_kerb:error] [pid 15793] [client
192.168.1.128:50150] krb5_get_init_creds_password() failed: Decrypt
integrity check failed, referer: https://c7server.localdomain.local/ipa/ui/
This happens both from an external browser (I enabled form authentication)
and from a firefox session launched from the ipa server itself after
configuring it for kerberos.
I don't want to mess with this thread so let me know if I have to open a
dedicated thread specifying for example CentOS 7 or you think it is ok to
get in here... so that I paste here other relevant info.

This is a completely different problem, it just means you do not have
appropriate tickets in your browser, which then probably prroceeds
trying to use the IAKERB mechanism, and fails.

Simo.

--
Manage your subscription for the Freeipa-users mailing list:
https://www.redhat.com/mailman/listinfo/freeipa-users
Go To http://freeipa.org for more info on the project

Simo Sorce

2015-02-20 14:06:09 UTC

Post by Dan Mossor

Post by Dan Mossor
[Fri Feb 20 00:45:35.603016 2015] [auth_kerb:error] [pid 1173]

[client

Post by Dan Mossor
10.1.1.17:54157] gss_accept_sec_context() failed: An unsupported mechanism was
requested (, Unknown error), referer: https://vader.dom.net/ipa/ui/

This looks like a culprit to me, though IDK what's its cause. Simo may
know more.

I do not know the cause of the above error, investigating.

Simo.

--
Manage your subscription for the Freeipa-users mailing list:
https://www.redhat.com/mailman/listinfo/freeipa-users
Go To http://freeipa.org for more info on the project

Dan Mossor

2015-02-20 15:00:08 UTC

<---snip--->

After approximately 15 minutes, I am kicked out of the active session - while
in the middle of using it - and cannot log back in.

So, the oddity continues. Firefox was at fault here - once I cleaned up
FF and configured it with the new certificate, these authentication
problems cleared up.

Login was
attempted from 4
browsers across two machines, and every time the login screen returns with
"Your session has expired. Please re-login."

Does it work if you use forms-based authentication or if you use CLI tool?

When I attempted to go to use the form based authentication from both
Firefox and Chrome, it brought up the page to configure the browser - it
did not present me with a login.

<----snip---->

[Fri Feb 20 00:45:35.603016 2015] [auth_kerb:error] [pid 1173] [client
10.1.1.17:54157] gss_accept_sec_context() failed: An unsupported mechanism was
requested (, Unknown error), referer: https://vader.dom.net/ipa/ui/

This looks like a culprit to me, though IDK what's its cause. Simo may
know more.
In a meantime you could try to enable debugging to get more info from
/var/log/httpd/error_log by creating /etc/ipa/server.conf and restarting
httpd.
# cat /etc/ipa/server.conf
[global]
debug=True
You could also open browser develeper tools (press F12) and inspect XHR
communication in network tab [1]. Check especially if some request to
/ipa/session/json or ipa/session/login_kerberos or
ipa/session/login_password does not end with 401 Unauthorized status
code. And then what's the cause of next 401 after series of 200. It
might contain some pointers. Like session expiration time and such.
[1] https://pvoborni.fedorapeople.org/images/ff-dev-tools-xhr.png

I was looking at the console last night, and unfortunately I didn't save
any of the error messages displayed. I can't recall the exact wording,
but the one clue I was able to get from the Firefox console was that the
certificate wasn't trusted - it said it was because it was expired, but
it was actually due to my not having granted the exception to the
self-signed cert yet. I was unable to do this due to the Firefox
glitches mentioned previously.

Have you modified Kerberos Ticket Policy or any Password Policy?

No, it was a default rolekit deployment - the only thing in my
settings.json file was the admin password.