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

Try clearing your browser cache.

Suggest an answer

Log in or Sign up to answer
Community showcase
Asked Thursday in Jira Ops

I'm John Allspaw, Ask Me Anything about incident analysis and postmortems

I'm John Allspaw, co-founder of   Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...

457 views 2 5
View question

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you