-
Bug
-
Resolution: Fixed
-
Medium
-
2.3.0
The Crowd SSO plugin will only enable SSO integration when it can. It tests:
- whether a User Directory has been set up pointing to Crowd.
- whether the remote Crowd has got a valid SSO cookie configuration.
The second test is causing problems because an empty cookie domain is a valid configuration, but the Crowd SSO plugin does consider it valid.
A workaround for now is to configure the SSO Domain in Crowd (Under Admin > General). Note that by configuring the SSO Domain in Crowd, SSO integration will only work when you access the applications over that domain. Make sure you don't set it to localhost, or all Crowd SSO integration will only work when you access the applications through localhost.
- is related to
-
BSERV-3346 NPE with SSO plugin enabled & Crowd directory set without SSO Domain
-
- Closed
-
It seems the other apps (Jira, Conf, etc..) will throw out a "localhost" value and continue to function. It's important that Stash does as well - there are times when running locally that I cannot use a FQDN and must use localhost.