Answered

Custom Connector for JIRA with 'Generic Oauth 2.0'

(0) Share

Report

Posted on by JPMontoya

Howdy,

I am currently trying to create a custom connector for JIRA as the pre-defined one does not cover all the needed functionality. However, I am getting stuck at trying to set up the Authentication. I have previously created a Custom Connector for the MS Planner, but there, the identity provider was not the 'Generic Oauth'.

Here, a lot of URL's are needed, which I am not sure (a) how to understand what they are for and therefore also (b) what I am supposed to enter.

I am familiar with the redirect URL at the bottom and that it will get generated for me, and I think I can just leave the Scope be as it is to get a default setup, but with the rest I am not sure what to do.

Screenshot 2020-08-10 at 13.59.43.png

any help / ideas are very welcome.

cheers,

Categories:

Using connectors

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

danielbazetto Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hello @JPMontoya

Power Platform Custom Connectors support OAuth 2.0 protocol. Atlassian is not an identity provider that we support OOTB in the custom connector designer, so please read this documentation from JIRA how to configure OAuth 2.0 in app management: https://developer.atlassian.com/cloud/jira/platform/oauth-2-authorization-code-grants-3lo-for-apps/

You need to use Generic in the identity provider, which lets you configure the token url and authorization url.

Was this reply helpful? Yes No
JPMontoya 81 on at

Like (0)

Report
Copy link

Link copied!

Hi @danielbazetto

Thanks for your response 😃.
I have stumbled upon that JIRA documentation as well and have not found it to be particularly intuitive (granted, I'm very new to all that authentication stuff, so maybe it is the gold standard for how to do such a documentation).
Additionally, the part with the authorisation URL looks to me like it would have to be user-specific or even session-specific, since the "state" part of the URL would have to be different for each user / session if I understand this correctly.
However, the Connector I am building will have to be used by many different users and the hassle of creating a Connector for each user seems disproportional, compared to the security benefits gained over simply using basic auth. with HTTPS.
If we also take into account the session-specific part, then I am not sure it can even be done within the constraints of what is possible with the authentication settings available in a Custom Connector. Afaik, the predefined/official JIRA Connector also uses basic auth. with HTTPS and an API Token, so ultimately that's what I opted for as well 😉.

Regardless, if someone wants to have a crack at it, then the documentation you linked is certainly the place to start.

Thanks again & best regards,
JP

Was this reply helpful? Yes No