-
Suggestion
-
Resolution: Unresolved
-
None
-
39
-
Hello everyone,
We are pleased to announce that we have released support for OpenID Connect for Jira, Confluence, Bitbucket and Jira Service Desk Data Center.
You can learn more about it here: https://www.atlassian.com/blog/enterprise/openid-connect
Please note that in order to use OpenID Connect you will need Data Center license.
You can create your evaluation license for your Data Center product here https://my.atlassian.com/license/evaluation
We hope that you will enjoy it!
Please reply directly to my email to share your feedback or just add your comments in this ticket. We'd love to hear your thoughts!
Best regards,
Marek Radochonski
Senior Product Manager
mradochonski@atlassian.com
OpenID Connect performs many of the same tasks as OpenID 2.0, but does so in a way that is API-friendly, and usable by native and mobile applications. OpenID Connect defines optional mechanisms for robust signing and encryption. Whereas integration of OAuth 1.0a and OpenID 2.0 required an extension, in OpenID Connect, OAuth 2.0 capabilities are integrated with the protocol itself.
Source:
http://openid.net/connect/
[CWD-3995] Provide support for OpenID Connect
| Support reference count | Original: 38 | New: 39 |
| Support reference count | New: 38 |
| Remote Link | New: This issue links to "Page (Confluence)" [ 629623 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 541530 ] |
| Remote Link | Original: This issue links to "Page (Confluence)" [ 540430 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 540430 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 517371 ] |
| Status | Original: Under Consideration [ 11774 ] | New: Future Consideration [ 11775 ] |
| Description |
Original:
{quote}
OpenID Connect performs many of the same tasks as OpenID 2.0, but does so in a way that is API-friendly, and usable by native and mobile applications. OpenID Connect defines optional mechanisms for robust signing and encryption. Whereas integration of OAuth 1.0a and OpenID 2.0 required an extension, in OpenID Connect, OAuth 2.0 capabilities are integrated with the protocol itself. {quote} Source: http://openid.net/connect/ |
New:
{panel:title=Atlassian Update - 28 January 2020|borderStyle=solid|borderColor=#3c78b5|titleBGColor=#3c78b5|bgColor=#e7f4fa}
Hello everyone, We are pleased to announce that we have released support for OpenID Connect for Jira, Confluence, Bitbucket and Jira Service Desk Data Center. You can learn more about it here: [https://www.atlassian.com/blog/enterprise/openid-connect] Please note that in order to use OpenID Connect you will need Data Center license. You can create your evaluation license for your Data Center product here [https://my.atlassian.com/license/evaluation] We hope that you will enjoy it! Please reply directly to my email to share your feedback or just add your comments in this ticket. We'd love to hear your thoughts! Best regards, Marek Radochonski Senior Product Manager [mradochonski@atlassian.com|mailto:mradochonski@atlassian.com] {panel} {quote} OpenID Connect performs many of the same tasks as OpenID 2.0, but does so in a way that is API-friendly, and usable by native and mobile applications. OpenID Connect defines optional mechanisms for robust signing and encryption. Whereas integration of OAuth 1.0a and OpenID 2.0 required an extension, in OpenID Connect, OAuth 2.0 capabilities are integrated with the protocol itself. {quote} Source: http://openid.net/connect/ |
| Workflow | Original: JAC Suggestion Workflow [ 3362918 ] | New: JAC Suggestion Workflow 3 [ 3629002 ] |