We have jira configured through Okta SSO as Identity provider (IDP). This works well for accessing JIRA tool thru OKTA sign-in. However, We need to access JIRA REST API to perform some admin operations in a external automation code. I cannot use Basic Auth because I do not have a jira username/password (we have SSO through Okta). * I am using jira server 9.17. * If I call the v3 api (sample: rest/api/3/serverInfo) using Personal Access Token, I get a url redirect to okta as response. * When I call the endpoint rest/api/2/serverInf , it works even if I don't pass any authorization. * If call other end point for example rest/api/2/application-properties using a personal Access token of a admin user I get 401 with the message "Client must be authenticated to access this resource." What is the process to call JIRA APIs through Okta SSO?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can I use jira server rest api with okta sso?

Daniele Silvestre de Souza

We have jira configured through Okta SSO as Identity provider (IDP).

This works well for accessing JIRA tool thru OKTA sign-in. However, We need to access JIRA REST API to perform some admin operations in a external automation code. I cannot use Basic Auth because I do not have a jira username/password (we have SSO through Okta).

I am using jira server 9.17.
If I call the v3 api (sample: rest/api/3/serverInfo) using Personal Access Token, I get a url redirect to okta as response.
When I call the endpoint rest/api/2/serverInf , it works even if I don't pass any authorization.
If call other end point for example rest/api/2/application-properties using a personal Access token of a admin user I get 401 with the message "Client must be authenticated to access this resource."

What is the process to call JIRA APIs through Okta SSO?

Accepted answers

Daniele Silvestre de Souza

Seems that if I send the request for version 2 it works.

All comments

Florian Bonniec

Hi @Daniele Silvestre de Souza

You can create a Personal Access Token and use it to authenticate.

Using Personal Access Tokens | Atlassian Support | Atlassian Documentation

Regards

Daniele Silvestre de Souza

Hi Florian,

I'v already done it and does not work, I get as answer a redirect url for okta.

<html>

<head>

<script

src="/s/ik737z/9170005/1cum173/4.3.11/_/download/resources/com.atlassian.plugins.authentication.atlassian-authentication-plugin:save-fragment/js.cookie.js">

</script>

if(window.location.hash) {var expirationDate = new Date(); expirationDate.setTime(expirationDate.getTime() + 60000 * 5); Cookies.set('atlassian-authentication-plugin-url-fragment_4f19fda7-8ab8-4e6e-b408-92d52ba88a91', window.location.hash.substr(1), {expires : expirationDate, path : '', secure: true, SameSite: 'None' });}window.location.assign("link to okta');

</script>

</head>

</html>

Endpoint: rest/api/3/serverInfo

Daniele Silvestre de Souza

Seems that if I send the request for version 2 it works.

Daniele Silvestre de Souza

Also need to flag allow api call, and not sure why but I needed to generate a new token.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-data-center

data-center