Seraph SSO Module Ignored by Confluence when Using LDAP/AD?

[J M]

I'm trying to create a custom SSO module in Seraph. The modual is trivial; it reads existing information available in the request object and returns the username of the previously-authenticated user. For Confluence, it's already a working installation. The users already exist in Confluence, Confluence is set to LDAP integration, and new users are created at first login when they don't exist. Based on the Seraph documentation, I've created a jar with the package in it and put it in the lib directory. I've configured web.xml and seraph-config.xml as specified in the documentation. However based on the log output, the SSO module is never consulted for a login request; I have a number of logging statements at the level of INFO that never appear. Is Seraph bypassed entirely when Confluence is using LDAP integration? Is the Seraph documentation still right for Confluence 5.x?

Thanks in advance.

[J M · Accepted solution]

I finally realized that the Seraph documentation is wrong and you have to extend ConfluenceAuthenticator and not DefaultAuthenticator.

[Davin Studer]

Are you trying to do NTLM authentication? If so, then I would direct you to the below link.

https://confluence.atlassian.com/display/SPCON/Configuring+Confluence+to+use+Jespa+for+NTLM+Authentication

[J M]

Not directly. The server-side is Linux + Apache + Tomcat where the Apache service has already performed an authentication based on SPNEGO+Kerberos.