Jenkins plugin Crowd2 pulled - can Atlassian help to reinstate this?

[Martin Dowie]

We use Jenkins with our Atlassian stacks and the Crowd integration is really useful...but has recently been pulled from the Jenkins plugin site: crowd2 | Jenkins plugin

This seems to be because of the license associated with the REST API, which isn't 'open' or 'open enough' for Jenkins/Github.

Could Atlassian do something about this? e.g. adopt more open licenses?

More details here: doc: add info about distribution restoration · jenkinsci/crowd2-plugin@34daf89 (github.com)

[Mark Hubers]

It's the same problem here, and we pay a lot more for DC software and get a lot less from Atalassian.  The only reason we pay for the crowd and now we may not be able to use it anymore.

[Jaedo Aum]

me too. We may not renew our subscription to Crowd DC next year because we're not using the Crowd2 addon, we're using it directly with AD.

[Ashwini_More _miniOrange]

@Martin Dowie

I would like to suggest miniOrange's Jenkins Crowd SSO App. We have developed an innovative solution to perform SSO with Crowd, allowing you to log in to Jenkins using Crowd credentials.

Please raise a service request here and a miniOrange representative will help you with all the details.

PS: I work for miniOrange, One of the SSO vendors in Atlassian Marketplace.