Use Automation with Okta

The features described in this article are currently rolling out and may not be available in your Jira Service Management project yet. Keep an eye on our release notes to find out when the feature will be available.

The Okta integration with Automation is only available to Jira Service Management Cloud customers on Premium or Enterprise plans. Find out how to upgrade your plan.

You can connect your Okta account to your Jira project to automate the process of employee onboarding and other HR tasks. You must be a Jira admin to connect Okta to Jira automation. Visit Okta's documentation to read more about registering a core API in Okta.

Configure an API in Okta

Before creating a connection between your project and Okta, you need to register an API client in Okta:

  1. Sign in to your Okta account as a user with administrative privileges.

  2. From the Admin Console, go to to Applications > Applications.

  3. Select Create App Integration.

    1. For the Sign-in method, select OIDC - OpenID Connect.

    2. For the Application type, select Web Application.

  4. Select Next.

  5. On the New Web App Integration page:

    1. enter an App integration name (eg. Jira - Okta integration)

    2. deselect the Proof of possession field

    3. for the Grant type, under Core grants, select the following checkboxes:

      1. Authorization Code

      2. Refresh Token

      3. Update Sign-in redirect URIs to https:id.atlassian.com/outboundAuth/start

      4. update Sign-out redirect URIs to https:id.atlassian.com/outboundAuth/finish

  6. Select an Assignment option according to your preference

  7. Select Save.

  8. Okta will create the app integration. From the new application General tab, copy the Client ID and Client Secret

    1. If you need to create a new Client Secret, you can go to the Okta API Scopes tab and create a new active secret.

  9. From the URL bar, copy the Base URL. For example: https://dev-1234567.okta.com. Remember to remove the -admin part of your subdomain.

Read more about registering a core API in Okta.

Make sure you have these three things before continuing to integrate Okta with Jira: Base URL, Client ID, and Client secret.

Integrate an automation rule with Okta

You can choose to create an automation rule with an action that integrates with Okta. Read more about creating an automation rule.

Each time you create a rule that integrates with Okta, you will need to create a connection using the details you received when you registered the API client in Okta.

  1. From your project settings, select Project settings, then Automation.

  2. Select Create rule and add a trigger.

  3. Select Add component and search for Okta actions by searching for “Okta” in the search box.

  4. When prompted to connect to Okta, select Connect.

  5. Complete the form with the details you received when you registered the API client in Okta (Base URL, Client ID, and Client secret).

  6. Select Connect.

  7. You will be taken to Okta for authorization.

    1. Sign in to Okta.

    2. When prompted to “Authorize Okta”, select Allow.

  8. Based on the trigger, fill in the form with the required fields

Actions

Create user in Okta

The Create user in Okta action allows you to create a new user in Okta using details about an employee from other services to use in your Jira project. This can be useful for streamlining your onboarding process and gathering employee details when resolving a query. For example, when a user is added to Workday, you might automate the next step to create a user in Okta using their Workday details. Learn more about Workday triggers.

Retrieve user details from Okta

This action allows you to retrieve certain employee details from Okta to use in your Jira Service Management project. This can be useful for verifying if the user already exists in Okta to avoid creating duplicates.

Smart values

You can use smart values to access data in Okta for use in your Jira project.

Action smart values

{{okta.user.department}} – Returns a user's department from Okta, for example: Engineering.
{{okta.user.displayName}} – Returns a user's display name from Okta, for example: Jane Doe.
{{okta.user.email}} – Returns a user's email address from Okta, for example: jane.doe@example.com.
{{okta.user.employeeNumber}} – Returns a user’s employee number from Okta, for example: EMP12345.
{{okta.user.firstName}} – Returns a user's first name from Okta, for example: Jane.
{{okta.user.lastName}} – Returns a user's last name from Okta, for example: Doe.
{{okta.user.id}} – Returns a user's Okta ID from Okta, for example: 00u1abc2def3ghi4.
{{okta.user.login}} – Returns a user's login username from Okta, for example: jane.doe@example.com.{{okta.user.manager}} – Returns a user's manager from Okta, for example: Jess Deer.
{{okta.user.managerID}} – Returns a user's manger ID from Okta, for example: 001xyz2abc3def4.
{{okta.user.mobilePhone}} – Returns a user's mobile phone number from Okta, for example: +1-555-555-5556.
{{okta.user.primaryPhone}} – Returns a user's primary phone number from Okta, for example: +1-666-666-6665.
{{okta.user.secondEmail}} – Returns a user's secondary email from Okta, for example: jane.doe.personal@example.com.
{{okta.user.status}} – Returns a user's status from Okta, for example: ACTIVE.
{{okta.user.title}} – Returns a user's job title from Okta, for example: Senior Software Engineer.

Still need help?

The Atlassian Community is here for you.