Replies: 3 comments 5 replies
-
The best way to handle this is to create an authentication location (say /path/login/page) which is the only one you protect with mod_auth_gssapi. In that location you will use ErrorDocument 401 to show a form to be shown as alternative authentication if krb auth fails. All browsers will do krb negotiation if they are capable or show the body of the 401 document if not. Either auth method should end up setting a cookie to carry auth into other locations (via SessionCookie module for example) and redirect to the actual application location on success. You can see an example of this in the freeIPA project. In the protected location you will want to set the following directives probably: #disable basic auth #use sessions so you can auth to other parts of the app #avoid some browsers to try their own "NTLM" dialog HTH. |
Beta Was this translation helpful? Give feedback.
-
Hello, I'm facing the same problem. When a visitor visits our page, and they are in our Kerberos realm, they automatically get logged in. When a Ideally, the visitor would be redirected to our manual login page instead of showing the popup Any help would be much appreciated! |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Is there a way to redirect a user to a certain page instead of showing the basic authentication dialog while not authenticated?
i tried already the ErrorDocument 401 directive, but this redirected all users to the given page.
in mod_auth_kerb there was the possibility to use Satisfy Any to tell the apache to do the kerberos authentication and to allow access even the auth failed.
source : https://www.jeffgeerling.com/blogs/jeff-geerling/apache-kerberos-authentication
is there something similar in mod_auth_gssapi?
best kind of regards
andreas
Beta Was this translation helpful? Give feedback.
All reactions