Dark Features

Kantega SSO’s dark features is a collection of toggles and tools to solve problems we have encounter while supporting clients when the use case is either too niche to have easily available in the GUI, or potentially breaking for Kantega SSO if used wrong. We recommend only using the dark features if you have been instructed by our support team to do so. Information about how to contact support can be found here: Requesting support

The dark features can be found at:

Kerberos User Lookup encoding

LDAP filter encoding is recommend, but can cause problems in certain setups. This dark feature disables the encoding.

Set KSSO config version for config updates

This dark feature is used when we want to trigger an automatic config update manually.

Clean up update failures

This dark feature removes update failure messages that persists even though the update was successful.

Crowd server config

When a user is looked up from an Atlassian Crowd Kantega SSO initiates a rest call to notify the crowd instance that the login has happened. When the same rest call is called against a Jira Crowd instance, this creates a warning in the Jira logs since Jira does not support this rest call.

And by default Kantega SSO tries to identify if the attached Crowd is either Atlassian Crowd or Jira Crowd (by looking at it’s name and URL). If this identification is faulty you may tune this on the Crowd server config table (see below). For the type api-connector Crowd instance it does not matter if the switch is turned on or off.

Open

Use legacy Kerberos

In Kantega SSO 6.26.0, we updated our Kerberos implementation. If, after updating to Kantega SSO 6.26.0, you run into problems with Kerberos authentication, we recommend to toggle this to see if it fixes the problem. If it does not fix the problem, please contact support so we can have a look at it.