> gss_accept_sec_context() failed: Unspecified GSS failure. > kerberos ticket (but) for HTTP/, which is not found > to, because it sends (actually the same) With InternetExplorer mod_auth_kerb declines the access > sends a kerberos ticket for HTTP/, which is found in Clicking the 'arrow' button next to 'Step 1' will download and begin the installation process of the helper software VirtualHostX uses to run a web server on your Mac.
#Virtualhostx installation tutorial install#
> still works, because firefox does a reverse and forward dns-look and The first time you launch VirtualHostX, youll be greeted with the Welcome Screen as shown here: Follow the two steps to install the software. > Using the MIT implementation, accessing the virtualhost using firefox Oktober 2010 20:02īetreff: Re: Different behaviour of mod_auth_kerb depending on kerberos stack We have to create one "big merged" keytab file, containing all generated above, which will be used by mod_auth_kerb.Ģ) Firefox will always deliver the ticket for service HTTP/ - no matter which virtualhost is accessed?ģ) Am I right, that the MIT kerberos implementation checks, if the referenced keytab file contains the service requested by the client and that this behaviour can not be changed? Keytab x will be generated for an account containing spn HTTP/ Keytab 2 will be generated for an account containing spn HTTP/ Keytab 1 will be generated for an account containing spn HTTP/. So at the moment using heimdal on sles11 would be the better option. It would be a gigantic effort to create separate accounts for each service - and that without impact on the running services.
The only limitation seems to be, that this only works with heimdal. "You cannot map multiple service instances to the same user account."īut on the other hand: we ARE currently running a setup with ~ 300 services shared in only a few accounts. This approves a note in the following guide I found at microsoft:
Previous message: Different behaviour of mod_auth_kerb depending on kerberos stack.AW: Different behaviour of mod_auth_kerb depending on kerberos stackĪW: Different behaviour of mod_auth_kerb depending on kerberos stack Beier Michael M.Beier at
0 kommentar(er)
