First of all: P2 vs. Connect
As Frank mentioned here "Using Atlassian Connect is not sufficient enough as you can by-pass requests.". Is this 2 years after still an issue? Or just inseparable part of the design of Connect?
As I'm planning to use third party applications like Google Authenticaor, is there anything speaking against using the rfc6238 standard? Are there better/more secure approaches since?
The general design approach would be a servlet-like filter that blocks all requests until a correct OTP for the user is entered. Is there something wrong with that?
If you know any useful literatur about this topic in general, please feel free to post your information under this question here! =)
Just for completness, as it probably answers the question:
"Simply put, it is not possible to implement custom authentication for Atlassian Cloud applications. Among other reasons, Atlassian has a shared authentication layer for our cloud services called Atlassian account, so JIRA Cloud does not even have APIs that you could extend. Additionally, you should expect that we will expand native support for 2FA from Bitbucket to the rest of Atlassian Cloud in the near future.
So hopefully that's enough to guide you towards building a P2 plugin for JIRA Server.
Hi awesome community! In this article, I would like to describe the one of the toolset (service) for the analyze some problems on different Java-based instances, of course, as Atlassian admini...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs