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,763
Community Members
 
Community Events
176
Community Groups

Has anyone had problems with multiple level subdomains using Crowd/SSO?

I have been able to connect most of our products to crowd, and individually they work as expected. I "enabled" SSO for products such as bamboo, stash, and confluence, and of course crowd. Here's the weird part, it works exactly opposite. For example, if I sign in to Stash in a browser, and then open a tab and navigate to confluence, the login page will appear (instead of the landing page, thinking i was already authenticated), and if i go back to the Stash tab, and refresh the page, the session will be expired there as well..

I have the domain in crowd set .mycompany.com

All my the applications are of the domains product.test.mycompany.com

 

One other thing that shouldn't make any difference, but each product is set up in crowd as 

application - > Directories (Active Directory and Local)

I have it this way so I can use the auto-add-to-group for each application, like for jira-users, but its by application and not across all users/products.

any ideas?

 

1 answer

0 votes

This sounds like the kind of situation that's going to require a few back and forth exchanges to figure out; would you please open a support request at https://support.atlassian.com so our support team can help out out? (You can just copy-paste your question initially.)

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events