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?
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:
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.