atlassian-test-docker

Prerequisites

127.0.0.1   crowd.test.net
127.0.0.1   jira.test.net
127.0.0.1   stash.test.net
127.0.0.1   bamboo.test.net
127.0.0.1   confluence.test.net

docker-compose up

docker-compose rm

Run the Crowd setup wizard and configure with Postgres database (CrowdID is already configured through environment variables in docker-compose)

create a crowd_admin initial user
- it will only be used for initial set up but by creating service specific accounts we can avoid clashes between Crowd and local users later when implementing SSO
create a user for yourself and give it admin rights on Crowd
create a test gmail account and use the gmail settings for the mail server
- Copy crowd.example.xml to crowd.xml and set your user name and password (use the full email address)
- needed to allow access for less secure applications on gmail account to get this to work
- use this JNDI location: java:comp/env/mail/SecureSmtpServer
Set the SSO domain under the general settings to .test.net

eventually the nginx gateway will timeout as JIRA restarts or something while creating the database
return to the base URL to continue with the wizard
create a jira_admin initial user
- it will only be used for initial set up but by creating service specific accounts we can avoid clashes between Crowd and local users later when implementing SSO
- seems to be ok to configure the same administrator user name, etc as supplied for Crowd but let's not anyway
set up JIRA for 'software development', ie. 'JIRA + JIRA Agile'

Add groups, etc. to the default Crowd directory (we don't want separate directories for different applications - we want single sign on)
use jira/jira for the application name and password to match the environment variables set in docker-compose.yml for the jira container
Use CIDR notation to specify the JIRA IP address, eg. 172.17.1.1/24 as the IP may change
when adding the crowd server URL to JIRA, remember to append /crowd, eg. http://crowd.test.net/crowd
add your user to the required jira groups in Crowd (especially admin)

create a stash_admin initial user
- it will only be used for initial set up but by creating service specific accounts we can avoid clashes between Crowd and local users later when implementing SSO
- seems to NOT be ok to configure the same administrator user name, etc as supplied for Crowd
  - The accounts do seem to get linked but the passwords do not (ie. changing the password in Crowd does not change the password required for Stash)
link to JIRA but don't use JIRA user database (will use Crowd)

Add groups, etc. to the default Crowd directory (we don't want separate directories for different applications - we want single sign on)
Add at least one group to add stash users to (eg, stash-users)
- It's a good idea to add other groups and set their permissions appropriately in Stash, eg.
  - stash-creators
  - stash-admins
  - stash-system-admins
- remember to add these to the stash application in Crowd as well
Use CIDR notation to specify the Stash IP address, eg. 172.17.1.1/24 as the IP may change
when adding the crowd server URL to Stash, remember to append /crowd, eg. http://crowd.test.net/crowd
to enable SSO with Crowd, log into the container and edit the ~/shared/stash-config.properties file via docker-compose run stash /bin/bash
- this will require a restart of Stash
add your user to the required stash groups in Crowd (especially admin)

Under application links in both applications enable all the Oauth options for both incoming and outgoing