Atlassian crowd implements Jira, confluence, bamboo and fisheye and crucible single sign-on __atlassian

Atlassian single sign-on involves the following products: Crowd, single sign-on, user management, JIRA, task tracking, confluence, demand management, Bamboo, sustainable construction, FECRU, code base management, code review;

Single sign-on requires the following conditions: crowd; domain access or the same server; The network relationship between different servers is smooth;

Just the following steps, these products are similar to the single sign-on step, the specific experience: Configure applications in Crowd, set up user management in Atlassian products (JIRA, confluence, Bamboo, Fecru), Add crowd directory, select authentication mode for crowd, configure Crowd.property, connect to crowd, configure Seraph.property, select login, authentication mode for crowd single sign-on;

Specific steps:
1. In CRWOD configuration applications, domain name, IP can be, but hosts or domain name server must be able to resolve this domain name, as well as to ensure smooth network relations;





2. Setting up user management in Atlassian products (JIRA, confluence, Bamboo, Fecru) to increase the crowd directory;


To modify the directory order:

3. Modify $ (Atlassion_home)/**/web-inf/ The Crowd.property in the classes directory, if not copied from elsewhere, modify the Applaction,password, which is the same as the applactions set above crowd;
Note: The fisheye and Crucible files are in the data directory.


4. Modify $ (Atlassion_home)/**/web-inf/ Classes directory of the Seraph.property, the user from the management of the change to SSO, this has a piece of code, remember fecru a bit different, it is not the code above, you need to add your own, and so I will flip out the code changes.

OK, so it's done, reboot your Jira or other product. Feel it.

Cond...