Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

SSO with Crowd Edited

Deleted user Apr 20, 2018

We have configured Crowd so that we can login with the default authenticator.

Our next step was to prepare SSO. So I followed the instructions and switched the authenticator lines in seraph-config.xml and copied and edited the file as required. 

After the confluence restart I cannot login any more. In the confluence log I see:

2018-04-20 12:46:01,066 WARN [http-nio-8090-exec-1] [atlassian.seraph.auth.DefaultAuthenticator] login login : 'mchjbaus' tried to login but they do not have USE permission or weren't found. Deleting remember me cookie.
 -- referer: | url: /dologin.action | traceId: 3af9dd70be01ca8a

In the Crowd log I see a LOT of lines like:

2018-04-20 12:45:45,863 http-nio-8095-exec-15 INFO [] Application 'confluence' failed authentication

 I have already reset the application's password so I am sure that the password in Crowd and the file is identical.

When I try to log in, I can see in the Crowd log that my userID is passed over to Crowd and is processed there via LDAP, but the result is always 'invalid user or password'.

Originally we had http://server.domain:8095/crowd and http://server.domain:8090 for confluence. We changed the latter to http://server.domain:8090/confluence - but the result is still the same.

1 answer

0 votes

Hi Jean,

 The error you are seeing:

Application 'confluence' failed authentication

is caused by the application properties in Crowd not matching what is being sent to Crowd from Confluence, one way or another. It can be caused by the source IP, the URL, the application name or password not matching what Crowd is expecting. 

When you added /confluence to the Confluence URL, was that in the or did you change the Base URL? Either way, if you add a context path it will need to be in the connector directive of the server.xml, as described in Configuring the Server Base URL. If you have a proxy in front of Crowd, please make sure the server.xml file discussed in that guide has the proxyName, proxyPort and scheme in the connector directive, as well.

Special characters in the application password need to be escaped in the file to log into a Crowd application: Special Characters in application password will break SSO authentication 



Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

306 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you