This is with regards to connecting Jira Service Management (AGC) with OKTA via Automation rules utilizing web service calls.
Does a static Okta API token (SSWS) would simplify implementation and work natively with JSM Automation is a best approach?
Alternately, Is it recommended to proceed with the OAuth JWT method and introduce a lightweight middleware service to:
This service is to automate the provisioning and deprovisioning of users from JSM portal onboarding/offboarding request forms. Note that an SSO is enabled using OKTA for accessing JSM.
I have implemented this before with the Okta automation integration:
https://support.atlassian.com/cloud-automation/docs/use-automation-with-okta/
How this looks like:
1. If you have the employee email address, use the create a user action
2. After, retrieve the user's details (id specifically from Okta) using the get user details action
3. Add the user to the appropriate groups in Okta that provide the application access required
In case there's anything custom you need to do, you can use the Send custom Okta request option where you can do a custom REST API call.
Hope this helps!
Andrea
Please note this automation connection with Okta is totally separate than what you are using in the provisioning of users for SSO through Atlassian Guard.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.