Here are the steps to install the solution with JIRA.
Step 1: Turn off JIRA
Step 2: Install the binary
- Retrieve the rsaaj.jar file from the Installation page.
- Retrieve the 3 extra binaries from Go2Group by creating a JIRA Issue at https://jira.go2group.com/browse/RSAA
- Install the binary to the
WEB-INF/lib
folder in JIRA- Example Location
$JIRA_INSTALLATION/atlassian-jira/WEB-INF/lib
Step 3: Edit the seraph-config.xml
- Locate your seraph-config.xml
- Example Location
$JIRA_INSTALLATION/atlassian-jira/WEB-INF/classes/seraph-config.xml
- Replace / comment the existing
<authenticator>
tag and replace it with Go2Group's custom authenticator:This is usually the default authenticator:
Example Location<authenticator class="com.atlassian.jira.security.login.JiraSeraphAuthenticator"/>
Comment it and replace it with:
Example Location<authenticator class="com.go2group.jira.rsaaj.RSAAJAuthenticator"/>
Step 4: Setup your license files
In the installation package, Clients should also receive a license file. Your license file should be in the format of rsaaj.license and must be installed in this location:
$JIRA_INSTALLATION/atlassian-jira/WEB-INF/classes
Step 5: Setup your binary configuration file
In the installation package, Client should also find two property files.
rsa-securid.properties
This property file is described below:
rsa_api.properties
This is the configuration file for the Solution using RSA's Authentication API to talk to the RSA Authentication Manager.
Important configurations to edit:
Key | Default Value | Recommended Value | Description |
---|---|---|---|
RSA_AGENT_HOST | _BLANK_ | _BLANK_ | This is the IP address for your RSA Authentication Manager. |
SDCONF_LOC | _BLANK_ | $JIRA_HOME/rsaa/sdconf.rec | Indicates the absolute path to the node secret that will perform the authentication for you RSA Authentication Agent. This file should be provided by the RSA Authentication Manager. |
SDSTATUS_LOC | _BLANK_ | $JIRA_HOME/rsaa/JAStatus.1 | Indicates the absolute path to the Authentication Manager server status file. |
SDNDSCRT_LOC | _BLANK_ | $JIRA_HOME/rsaa/nodesecret.rec | Indicates the absolute pathto the Authentication Manager node secret file. This file should be provided by the RSA Authentication Manager. |
Step 6: Start JIRA and log
After setting up the above, Client's can test their login by entering the username and RSA SecurID token and Atlassian password (depending on the rsa-securid.properties). For example, with the following configuration:
- rsasecurid.enable is true
- rsasecurid.factor is two
- rsasecurid.token.separator is \\|
The user needs to login with the username of <username> and password equaling to <securid_token>|<atlassian_password>.
- Username: rsaajtester
- Password: 84342143|rsaajpass