Use external Oauth provider to authenticate customers for service desk / portal / knowledge base

[Vidar Løvbrekke Sømme]

We would like to avoid our application users to have to have a separate login to get help and support.

Is there any way we can use our existing Oauth2/ OpenId Connect authority for authenticating our users as customers towards Jira service desk portal?

[somethingblue]

Hi Vidar,

There is a knowledge base article titled Allowing OAuth access that you may be interested in:

Your Jira administrator must establish an OAuth relationship with this external web application or instance by approving it as an OAuth consumer. For example, if you want to add a Jira gadget to your Bamboo homepage and allow this gadget to access your restricted Jira data, then your Jira administrator must first approve Bamboo as an OAuth consumer.

The Jira gadget on the 'consumer' is granted access to your Jira data via an 'OAuth access token', which acts as a type of 'key'. As long as the consumer is in possession of this access token, the Jira gadget will be able to access Jira data that is both publicly available and privy to your Jira user account. You can revoke this access token at any time from your Jira user account, otherwise, all access tokens expire after seven days. Once the access token is revoked or has expired, the Jira gadget will only have access to publicly available data on your Jira instance.

An OAuth access token will only appear in your user profile if the following conditions have been met:

1. Your Jira Administrator has established an application link using OAuth between your Jira instance and the consumer. Jira Administrators should refer to Using AppLinks to link to other applications.

2. You have accessed a Jira gadget on a consumer and have allowed this gadget access to your Jira data. See Issuing OAuth access tokens below for details on this process.

Take a look at the full article for more information and steps to link your OAuth provider and JIRA.

Cheers,

Branden

[Vidar Løvbrekke Sømme]

No,, that is not what I am looking for.

This describes allowing other consumers on the Jira id Authority.

What I am asking is to have jira servicedesk accept my authentication service as the authority to authenticate customers.

[Torbjörn Bång - Twoday]

Hi, did you find a good answer to this?

[Ershad Sakkaki]

Hi Brenden- That is very helpful. As you mentioned, all access tokens expire after seven days. Is there any way to extend that to 30 or 60 days?

We don't want our users to get a pop-up every 7 days to allow application's ('consumer') access to jira.

[Angus Warren]

If you're using On Prem, this marketplace app does the job really nicely. https://marketplace.atlassian.com/apps/1217688/oauth-openid-connect-oidc-for-jira-sso?hosting=server&tab=overview

With the new Azure AD oauth process, you can allow any Office 365 tenancy account, or even personal Microsoft accounts to be used for authentication.

[Johannes Spangenberg]

Maybe OpenID Connect for Data Center - Work Life by Atlassian resolves this issue? It looks like Atlassian has released such functionality in 2020. The functionality should either be included within the product or available via the SSO for Atlassian Server and Data Center plugin.