Hi Dave,
I am curious to know if we have any plans to have this feature soon? (Last update was on 2016, hoping the situation may have got better?)
We're in evaluation phase, (and eventually may move to cloud instance, but at the moment) we have a $10 Service Desk self-managed server. Without native support for this feature, the plugin may cost about $175 (for 100 users) – isn't quite in the right proportion of the server pricing itself. While I'm not looking for any off-pricing on the plugin, I do have high expectations from Atlassian products in general and definitely expected OpenID provider support built-in.
Thanks!

While OpenID add-on "looks great" it does not work as expected and has general flaw — it doesn't set "remember me" token which cause serve usage annoyance, especially for Windows users, where application is considered to be quit once all its windows are closed.

Any news? Thanks

I see this an a massive enabler for AoD.

The plug-in for OpenID looks great, unfortunately it is not available in onDemand instances.
Besides voting for this issue, what can I do to push for this issue to be solved (included in onDemand)

Is there a supported, native alternative to OpenID which achieves a similar flow using Crowd i.e. what's in use when authenticating at id.atlassian.com ?

Just to let you know I've published a plugin that addresses this issue https://marketplace.atlassian.com/plugins/com.pawelniewiadomski.jira.jira-openid-authentication-plugin

Any progress here? This would be REALLY helpful for OSS projects. Many users don't like to register just to report an simple issue.

Support for OpenID would be amazing! Please Atlassian, implement this. Pretty please?

Where can one get the plugin you speak about?

Well the fact that a plugin exists is a beginning.
But a plugin means that only some installations will offer it.
Where I work we use a corporate JIRA with a specific SSO system and I think we won't go for OpenID for the moment.
But, since I'm using a lot of open source project which uses JIRA it means that I need to register on each of them ... which I do with the same login and password. From the "Single Point Of Failure" analysis this means that if any of those server got compromised all my JIRA accounts will be compromised. This is a heck of a problem for me.

By the way, did I mentionned none of them where offering OpenID support ?

A Janrain developed JIRA plugin exists. We have used this some but not extensively since we have migrated from JIRA hosted to JIRA Studio SaaS. The plugin is not yet allowed for JIRA Studio. Atlassian was not comfortable supporting the plugin for their multi-tennant JIRA Studio SaaS offering back when the plugin was initially developed. Need Atlassian to comment if they will now support this plugin for JIRA Studio.

NOTE: This plugin is open source. Contact Janrain to find where the source is managed.

My accounts to post on JIRA bug tracking systems are multiplying: Hibernate, Grails, Atlassian itself, Spring... add support for OpenID, please!

I am pursuing funding approval for development of a JIRA RPX plugin. The
scope I am looking at is ...

Scope
Develop a Java JIRA RPX plugin
Development and testing to be done with JIRA Version 4.0.2 enterprise
Plugin to use Janrain RPX to handle the OpenID transaction
Plugin will authenticate an existing JIRA User
Existing user will be found by an RPX mapping to username, or email
address to username
OpenID login will be initiated by a dashboard gadget
Plugin will be made open source

Out of Scope
Final UI for dashboard gadget
Creating/Provisioning/Bootstrapping Jira User and mapping to OpenID
Additional versions of JIRA beyond 4.0.x

By making this open source, I am hoping Atlassian or the community will
pick this work up, keep it current with future JIRA versions and address
the out-of-scope work listed above. I also hope Atlassian will make this
JIRA RPX plugin available to JIRA Studio. My prediction is that I will get
approval to proceed and the plugin will be completed and made open source
within the next month.

Will this be helpful to you? How might you leverage and add to this???

Steve C. Braunschweiger
IT Architect & Security Analyst
IS WW APPLICATION TECHNICAL SUPPORT

Eastman Kodak Company
343 State Street
Rochester, NY 14650-1245

steven.braunschweiger@kodak.com
Office: 585 724-1417
Mobile: 585-704-4096
www.kodak.com

From:
"Peter Sankauskas (JIRA)" <jira@atlassian.com>
To:
steven.braunschweiger@kodak.com
Date:
04/07/2010 01:49 AM
Subject:
[JIRA] Commented: (JRA-13942) OpenID support for authentication

[
http://jira.atlassian.com/browse/JRA-13942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190917#action_190917
]

Peter Sankauskas commented on JRA-13942:
----------------------------------------

Any update on the progress for JIRA supporting OpenID? It makes a lot of
sense for all of the open source projects out there

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.
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.

–
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.atlassian.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Any update on the progress for JIRA supporting OpenID? It makes a lot of sense for all of the open source projects out there

My need is for JIRA Studio to accept authentication from an OpenID Provider other than CROWDID.
In my case, this OpenID Provider would be a private Kodak OpenID Provider.

The reason for this requirement is to enable Kodak to leverage its central user authentication, provisioning/de-provisioning and account management process targetted for use across all applications we host externally. We do not want the excessive overhead, varying levels of security and lack of single-identity/ single-signon that results from deferring to the authentication and account management model specific to each externally hosted application.

I figured Atlassian was embracing OpenID given the OpenID Provider that comes with CROWD (CROWDID). The issue is that I already have a Kodak OpenID Provider that provisions and manages Kodak branded OpenID accounts in a Kodak on-premise account directory. I simply need a hosted JIRA Studio instance for Kodak to behave like an OpenID Relying Party that accepts authentication from a single (Kodak) external OpenID provider.

If JIRA Studio were a true OpenID Relying Party, I could see an account administrator back-channel process prior to first login with external OpenID (possibly manual to start) that would be needed to setup a user profile in the JIRA Studio CROWD directory that would contain the user's groups and roles for project specific access rights. Ideally, this profile setup could be automated through JIRA Studio exposure of the CROWD REST api ... http://confluence.atlassian.com/display/CROWD/Crowd+REST+APIs

Considering how widespread Jira is in the open source project universe, it would be indeed really, really great if it supported OpenID aithentication. It's tiring to create one-time accounts to report a bug all the time.

OpenID support would be great, it would make submitting bug-reports (or posting a comment) a lot easier. No need to open a one-time account ...