Use Case:- Create Jira account for a user and assign a specific group.
Hi,
I tested user provisioning for Jira source and found that wrong group was assigned to the user. The Access profile only had 1 entitlement, which was “confluence-users”, however after requesting the role from Request center, “jira-users” group was assigned.
I am using a Web services connection for Jira, and this is the current configuration:- Jira > Edit Configuration > HTTP Operations > Create Account > Body:-
{
"name": "$plan.username$",
"password": "$plan.password$",
"emailAddress": "$plan.email$",
"displayName": "$plan.fullName$",
"applicationKeys": [
"$plan.applicationKeys$"
]
}
Here as you see we are using application Keys. Application keys under Create Profile is set to a static value “Jira-Software”. This applicationKey in Jira has a default group “jira-users” added. It looks like as we are not specifically passing the entitlements in the body and just using applicationkeys, the “Jira-Software” plan is being initiated in Jira, and jira-users group is being assigned. Now as Jira-users is the default, and we are not mentioning any other groups in request, the entitlements in the access profile are being ignored.
SailPoint documentation https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-users/#api-rest-api-2-user-post mentions that applicationkeys is deprecated. I would like to know if there is a better way of doing this. What are the alternatives to using application keys?