Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,458,056
Community Members
 
Community Events
176
Community Groups

Crowd Mismatch token while SSO between JIRA and thrid party app. Can someone assist?

I am assuming that somehow my validation factor isn't good enough to accept the token for another application, though I can login into third party application and JIRA separately via crowd authentication. Here is the snippet of the logs:

 

017-10-29 06:04:41,604 http-bio-8095-exec-13 DEBUG [manager.token.factory.TokenKeyGeneratorImpl] Generating Token for principal: AroraRahul

2017-10-29 06:04:41,604 http-bio-8095-exec-13 DEBUG [manager.token.factory.TokenKeyGeneratorImpl] Adding remote address of 10.34.7.134

2017-10-29 06:04:41,604 http-bio-8095-exec-13 DEBUG [manager.token.factory.TokenKeyGeneratorImpl] Adding Random-Number of ValidationFactor[Random-Number=7647594814225824346]

2017-10-29 06:04:41,604 http-bio-8095-exec-13 DEBUG [crowd.manager.authentication.TokenAuthenticationManagerImpl] Current Validation Factors:

ValidationFactor[remote_address=127.0.0.1], ValidationFactor[X-Forwarded-For=10.34.7.134]

2017-10-29 06:04:41,604 http-bio-8095-exec-13 DEBUG [crowd.manager.authentication.TokenAuthenticationManagerImpl] comparing existing token Token{identifierHash='sLfTZcWbBQaW55xqhy9QRQ00', lastAccessedTime=1509271459529, createdDate=2017-10-29 06:04:20.0, duration=null, name='AroraRahul', directoryId=32770} with a validation token Token{identifierHash='ZUekGOFZ0GxdRxq5aFjLNw00', lastAccessedTime=1509271481604, createdDate=Sun Oct 29 06:04:41 EDT 2017, duration=null, name='AroraRahul', directoryId=32770}

2017-10-29 06:04:41,604 http-bio-8095-exec-13 DEBUG [crowd.manager.authentication.TokenAuthenticationManagerImpl$TokenValidationFailure] Existing token 'E4NHkpy3nQWUZSy9ghUDpA00' for user 'AroraRahul' does not match new token 'Ht61ZiIz09sl74cusjfcow00' with validation factors 'ValidationFactor[remote_address=127.0.0.1], ValidationFactor[X-Forwarded-For=10.34.7.134]'

2017-10-29 06:04:41,605 http-bio-8095-exec-13 DEBUG [crowd.manager.authentication.TokenAuthenticationManagerImpl] The token keys don't match

 

3 answers

Actually my issue was occurring from third party side which was trying to access the crowd for single sign on and unable to pass x-forwarded IP to perform consistent IP address with my JIRA application and failing to match the token for SSO between Jira and third party app.

 

Issue was resolved when I added the code to pass x-forwarded IP to the crowd instead of remote IP address.

Awesome, nice one!

Hello,

I've stumbled into this issue myself however we found that in Crowd we needed to untick the tick box that says "Require consistent client IP address" under the Session Configuration setting menu.

We were getting pretty much the same error message as you so if you're still having trouble I hope this helps!

 

Thanks,

Matt

0 votes
edwin Rising Star Oct 29, 2017

Try clearing your browser cache.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events