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

Changing SSO Cookie name in crowd does not change the name of the Cookie


I am looking to enable SSO over our internal atlassian products and to deny the possibility mixing up with any other SSO cookie for Atlassian from our customers. We decided to give it an original name.

But we note that when we log in that the default token name "crowd.token_key" is still being utilized.

We have tried to locate where the value is being set in a properties file, we located the documentation "" but with the notice that this file is not used from the crowd version 3.0+ and instead the attribute is stored in the database instead.

My question is where is this "SSO cookie name" attribute stored in the Crowd database for postgresql.
Or if that is the wrong assumption where do i locate where the Crowd "SSO token name" is being stored?

We are running crowd on version 3.2.2 with a connection towards a Postgresql DB version 9.6

Best regards
Pontus Ridderström

1 answer

1 accepted

1 vote
Answer accepted
Bruno Vincent Community Leader Aug 14, 2018

Hi @Pontus Ridderström

In Crowd's administration console, go to Settings > General > Single Sign-On cookie settings


Hi Bruno

Thanks for your answer, i have however already made that change.

When checking towards our Confluence, Jira, Bitbucket the token that is generated when logging in is still named "crowd.token_key"

Best regards

Bruno Vincent Community Leader Aug 14, 2018

@Pontus Ridderström

You probably need to restart those three applications to take the changes into account.

If this still does not work, you can override the cookie name in each application file (e.g. atlassian-jira/WEB-INF/classes/ by setting the cookie.tokenkey property:

cookie.tokenkey my.cookie_name

(You will have to restart each application afterwards)

Awesome thanks alot.

This solved my original question.

Have a great day :D

Suggest an answer

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

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

239 views 12 14
View question

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