Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-13942

OpenID support for authentication

XMLWordPrintable

    • 7
    • 8
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Atlassian Update - 28 January 2020

      Hello everyone,

      We are pleased to announce that we have released support for OpenID Connect for our Data Center products.

      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

      It would be useful for me to support openid authentication in Jira. I plan to build set of all web services based on openid authentication, so external users can use own openid server, and they do not need to register specifically with my Jira.

      OpenID would be similar to external LDAP - it only manages passwords. If Jira is in Public mode then new users may get some default user role (e.g. jira-users) after first log on, if Private then unknown OpenIDs should be just rejected.

        1. image.gif
          image.gif
          0.7 kB

              mradochonski@atlassian.com Marek Radochonski (Inactive)
              283904f5e802 Jaak Laineste
              Votes:
              118 Vote for this issue
              Watchers:
              59 Start watching this issue

                Created:
                Updated:
                Resolved: