You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have migrated one Jira instance to another test instance , the migrated data is from Jira instance which is connected with Crowd.
I am trying to connect new migrated Jira instance with Crowd but i am facing problem due to following error.
Connection test failed. Response from the server:
com.atlassian.crowd.exception.ApplicationPermissionException: HTTP Status 403 – ForbiddenType Status ReportMessage Client with address "10.100.4.219" is forbidden from making requests to the application, jirastg.Description The server understood the request but refuses to authorize it.Apache Tomcat/8.5.34
I have done following work around
Note: if you are migrating/upgrading a Jira instance that already uses Crowd, you will need to merge these files (not overwrite them).
- If Jira is running, shut it down first.
JIRA/atlassian-jira/WEB-INF/classes/seraph-config.xmlfile. Comment out the
Uncomment the line that contains the new authenticator:
- Copy the
JIRA/atlassian-jira/WEB-INF/classes/crowd.properties. Change the following properties:
The application name must match the name that you specified when you defined the application in Crowd (see Step 1 above).
The password must match the one that you specified when you defined the application in Crowd (see Step 1 above).
If your Crowd server's port is configured differently from the default (i.e. 8095), set it accordingly.
crowd.base.url must be the same URL used to access Crowd in your Browser.
Set to 0, if you want authentication checks to occur on each request. Otherwise set to the number of minutes between request to validate if the user is logged in or out of the Crowd SSO server. Setting this value to 1 or higher will increase the performance of Crowd's integration.
The problem was the migrated jira instance had a old crowd credentials in crowd.properties file and new server and crowd server subnet ip address were different.
Solution: Edited crowd.properties file with latest crowd credentials and added both servers in same subnet group.