Custom SSOAuthenticators do not work after upgrading to Confluence 3.4 and above

Still need help?

The Atlassian Community is here for you.

Ask the community

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

  1. Backup up the file <confluence-install>\confluence\WEB-INF\lib\atlassian-seraph-2.3.3.jar
  2. Replace it with the file in atlassian-seraph-2.3.3-patched.jar
  3. Restart Confluence

Last modified on Feb 26, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.