How can I pre-choose a site when authenticating with auth.atlassian.com in Jira cloud?

[Gray Watson]

I am authenticating a command-line tool by bouncing my users through an URL something like https://auth.atlassian.com/authorize?audience=api.atlassian.com&client_id=...&scope=read%3Ajira-work+write%3Ajira-work+read%3Ajira-user&redirect_uri=...&response_type=code&prompt=consent

This takes me to a https://api.atlassian.com/oauth2/authorize/server/consent URL which has some details about my app and asks me to "Choose a site" from the list of our production and development sites in Jire Cloud.

Is there any way to pre-select the site in the drop down or better yet, pre-select the site without the ability of the user to change it?

Thanks.

[Andy Heinzer]

Hi Gray,

I understand that you are trying to pre-define which Atlassian cloud sites would appear in this integration handshake.

To the best of my knowledge, it cannot be setup to pre-define these in the way you want.  Part of the problem is that when an end user gets this prompt, the user has to authenticate to Atlassian as a per-requisite just to get that screen.  That auth process then is used to lookup which sites that user is a member of.  That lookup populates the possible sites this user could choose to integrate this app with.

If there was hypothetically a means to do this, I still would not recommend doing it that way.  Basically because it could cause further customer problems when trying to setup this integration.  For one thing, a Cloud site's URL has the potential to be renamed/changed.  Hard coding which site the user should select could break their ability to integrate if say the site URL changed.  Instead the lookup that happens when the user logs into Atlassian's cloud services is a better dynamic means to handle which options are actually valid to that specific end user.

Are you building a Forge or an OAuth 3LO app yourself?  If so, then I think this is something that could be restricted within the app itself.  That is to say, I believe that such apps can restrict which sites they are functional in, and which they will not work with.  It's not exactly the same as restricting it at the specific stage you have referenced in your screenshot.  I don't have the exact details on how this is configured within the app itself, but I would recommend reaching out to our ecosystem helpdesk for further support on this topic.

[Jehan Bhathena]

Hi @Gray Watson ,

The image that you've shown in an End User Consent, it cannot be pre-set or pre-filled, it would defeat the purpose of allowing the user to choose weather to consent to the site or not.

I have tagged the atlassian team in this thread to get their inputs on this too.