Custom SSOAuthenticators do not work after upgrading to Confluence 3.4 and above
Symptoms
The custom authenticator fails to log the user in.
Cause
In the custom authenticator code uses the Request.getRemoteUser() method.
There is a bug in the bundled Seraph package which causes Request.getRemoteUser() to return null when called (even though the user has been successfully authenticated).
Resolution
- Backup up the file <confluence-install>\confluence\WEB-INF\lib\atlassian-seraph-2.3.3.jar
- Replace it with the file in atlassian-seraph-2.3.3-patched.jar
- Restart Confluence
Last modified on Feb 26, 2016
Powered by Confluence and Scroll Viewport.