Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

In House Application Registration

Andre Liebetrau November 15, 2021

I have a non web based inhouse application that I want to interface to Jira to create new Issues etc. I have tried the Service Account route but that required the users to log out of their own accounts before using the app.

What is the process to get this non web based inhouse application registered so we can use our existing login to access the Jira API with OAuth2 


Looking at https://developer.atlassian.com/cloud/jira/platform/oauth-2-3lo-apps/ . it requires a Privacy Policy URL. Since our app is non Web based what do I input here?

Also will we be able to use localhost as the callback URL for code grants?

1 answer

1 accepted

0 votes
Answer accepted
Neil Mansilla
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 30, 2021

Hello @Andre Liebetrau Just an FYI.. for development questions like this, I recommend you check out the Developer Community forums at https://community.developer.atlassian.com. But since you're here already, I'll do my best to answer your questions. :-) 

 it requires a Privacy Policy URL. Since our app is non Web based what do I input here?

Even though you're building an app that's for in-house/company use, you're still asking end-users to authorize your app to act on their behalf. If your company has an official privacy policy posted online, you may consider referencing that link; however, it's best to discuss this with your legal counsel or business leadership.

Also will we be able to use localhost as the callback URL for code grants?

TBH, I didn't think it would work, but lo and behold, it sure does. That being said, I imagine you're only going to use localhost during the development/testing phases, because otherwise, in order to do the auth code --> bearer token exchange, each user that authorizes this 3LO app will need to have a service running on their local machine (along with client secret to perform exchange), which isn't recommended.

Hope this helps!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events