Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


How to use a client token to authenticate on crowd server



Actually, I have a web service which is requested by my website, and I would like to use this web service to request an other web service which need crowd authentication.

The clients have a crowd token given by an other website which authenticate them on the crowd server and i would like to use this token on my web service to authenticate them on the crowd server. And by this way the web service can do request by their access and their name.

But it work if I use the to create a token with their user password, but if i copy past or get the token from the authentication website it didn't work.

It's close from this organization:

I'm sorry if it isn't very well explained, don't hesitate to ask me if you have any question.

Thanks in advance.

1 answer

1 accepted

0 votes
Answer accepted
Bruno Vincent
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jun 01, 2019

Hi @theo 

Let's sum up what you have here:

User's Browser -> Web application -> Web Service A -> Web Service B

What you are facing here is what is detailed in the 'Cause' section of this KB.

From Web Service B's perspective, requests come from Web Service A's IP address, whereas the Crowd token that was initially generated was tied to your user's IP address.

You have two options here:

  • Option #1: uncheck 'Require Consistent Client IP Address' in Crowd's console as detailed here
  • Option #2: add the IP addresses of Web application and Web Service A to the list of trusted proxy servers in Crowd's console and make sure to add the user's IP address, Web Application's IP address and Web Service A's IP address (in that order) to the X-Forwarded-For header as detailed here 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events