garysweaver
commented
11 years ago Thanks for the report!
Looks like this is failing:
getEventPublisher().publish(new LoginEvent(this, username, request.getSession().getId(), remoteHost, remoteIP));Can't fix right now, but should be able to take a look this evening.
If you want to follow the setup in the README, you might be able to work on a fix also.
Here is what Joe Clark (Atlassian Dev Relations) had done last year: https://bitbucket.org/jaysee00/example-confluence-sso-authenticator/src/381eb95ebc08/src/main/java/com/atlassian/confluence/seraph/example/ExampleSSOAuthenticator.java#cl-120
i.e.
putPrincipalInSessionContext(request, user);
getElevatedSecurityGuard().onSuccessfulLoginAttempt(request, username);
// Firing this event is necessary to ensure the user's personal information is intialised correctly.
getEventPublisher().publish(new LoginEvent(this, username, request.getSession().getId(), remoteHost, remoteIP));
LoginReason.OK.stampRequestResponse(request, response);
log.info(String.format("Login for user %s successful.", username));
return user;One difference is that he is using getElevatedSecurityGuard() and we were using:
getLoginManager().onSuccessfulLoginAttempt(username, request);But there are probably other differences, even though they weren't mentioned in what I had received here:
- https://developer.atlassian.com/display/CONFDEV/Preparing+for+Confluence+5.0
- https://developer.atlassian.com/display/CONFDEV/Browse+Menu+and+Space+Tools+changes+in+Confluence+5.0
I've just ensured that the authenticator shows up in marketplace as incompatible with 5.x until we can get this worked out.
bananastalktome
Using version 2.1.16 with Confluence 4.3.5 works fine, however when I tried upgrading to 5.0 (and also to 5.0.1) and attempt to log in in through Shibboleth I get an 'Oops - an error has occurred' page, and am not logged in. I get the following in the Confluence logs: