How to use Application authentication to also use the JSM Ticket tracking system?

[Sathishkumar Sundaram]

I have a client facing application which uses oAuth for identity resolution. We would like to use a JSM based Ticket tracking system for both client and internal domain users, but the authentication still should be managed by oAuth identity resolution. 

The idea here is to minimize the number of id/pwd users having to manage.

If the application and ticket tracking both could use the same identity resolution, it would be helpful. Please let me know if there are projects/use cases that already manages. If yes, how can we achieve this?

Appreciate your time and response.

Thanks,

Sathish

[Arkadiusz Wroblewski]

Hello @Sathishkumar Sundaram ,

JSM Cloud doesn't actually "reuse" your app's OAuth login.

Instead, the standard approach is to have both your app and JSM point back to the same central Identity Provider. While your app sticks with OAuth or OIDC, you connect Atlassian to that same IdP using SAML via Atlassian Guard for your employees

If you’re supporting external clients, you’ll need to configure the specific "Portal-only customer SSO" path within JSM settings, as that’s handled differently than internal staff accounts.

Essentially, you’re creating a shared identity hub rather than trying to daisy-chain the two systems together. Just a heads-up: you’ll need Organization Admin rights to handle the Guard and IdP side of this setup

.

[Jorge Cammarota]

The only way I know to do this would be through this method: using Atlassian Guard with SSO via SAML/OAuth through a centralized Identity Provider (IdP).

The key point is that the IdP is the centralizer. Both your app (via OAuth) and the JSM (via SAML/OIDC through Guard) point to the same IdP, eliminating the need for multiple credentials.

I hope this helps!