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,559,321
Community Members
 
Community Events
184
Community Groups

sso crowd+ldap+jira+Crucible/Fisheye

crowd2.4.10+jira5.1.8+Crucible/Fisheye2.10.1

JIRA and Crucible were connected to a Crowd server setup with an LDAP directory.

I can use a user from crowd to login in jira.And I can also the same user to login in crucible with the same username and password.

When I login in jira , I have still to enter username and password to login in crucible.SSO between jira and crucible isn't work.

The SSO Optional about seraph-config.xml and crowd.properties is already changed in JIRA.

I do not understand why the SSO isn't work in jira and crucible.Is there anythings I missed?

What the reason?

5 answers

0 votes
Caspar Krieger
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 19, 2013

I think you should read Crowd's documentation, especially An Overview of SSO, carefully; that page tells you how to configure each application. However, it's a prerequisite of that to already have the applications accessible through sub domains of whatever domain you pick, so I suggest you get that working first before you tackle getting SSO working (because SSO definitely won't work if you're accessing applications on different ports or IPs).

I found the domains were not set.I used ip not domain.

eg:

http://172.21.1.2:8095/crowd

http://172.21.1.2:8080/jira

http://172.21.1.3:8888/cr

The older version about crowd1.3+jira3.2+confluence2.7 seemed not using domains.

How to set domains in crowd+jira+confluence+crucible?

How to set domains like the following?

http://172.21.1.2:8095/crowd -> http://crowd.example.com/

http://172.21.1.2:8080/jira -> http://jira.example.com/

http://172.21.1.3:8888/cr -> http://cr.example.com/

In Crowd, go to 'Administration' -> 'General Options' -> 'SSO Domain'.

In jira or crucible,what can I do?

0 votes
Caspar Krieger
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 19, 2013

It's not the machines which matter, but the domain names through which users are accessing each app (and hence also whether the cookie config for each of the apps is correct). What domain names are the apps under?

Crucible and CROWD are in the same machine,JIRA is in another machine.Is the reason?

0 votes
Caspar Krieger
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 18, 2013

Have you got Crucible/Fisheye and JIRA sharing a domain? (That's a prerequisite for SSO to work, because cross-domain SSO isn't supported yet - more info here)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events