mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2026-09-03 20:52:56 -05:00
Finn Krein-Schuch
2dcc943e6b
In some user agents (e.g. Chrome on Windows) after negotiation of Kerberos auth fails the agent will try negotiating NTML auth. This will not work but may prompt http basic auth popups before showing the html login form, confusing the users. To circumvent this problem mod_auth_gssapi added the option GssapiNegotiateOnce, sending the negotiate header only once. References: [1] Discussion in mod_auth_gssapi: https://github.com/gssapi/mod_auth_gssapi/discussions/293 Fixes: https://pagure.io/freeipa/issue/5614 Signed-off-by: Finn Krein-Schuch <finn.krein-schuch@sva.de> Reviewed-By: Alexander Bokovoy <abokovoy@redhat.com>
Ground rules on adding new schema Brand new schema, particularly when written specifically for IPA, should be added in share/*.ldif. Any new files need to be explicitly loaded in ipaserver/install/dsinstance.py. These simply get copied directly into the new instance schema directory. Existing schema (e.g. in an LDAP draft) may either be added as a separate ldif in share or as an update in the updates directory. The advantage of adding the schema as an update is if 389-ds ever adds the schema then the installation won't fail due to existing schema failing to load during bootstrap. If the new schema requires a new container then this should be added to install/bootstrap-template.ldif.