Is crowd obsolete since jira has its own internal user server?

[ChristianW]

I have 2 confluence servers and 1 jira server connected to one crowd server. Since Jira has its own internal user server i wonder if we still need crowd. The docu says that different jira and confluene servers can connect to one jira which can also delegate requests to ldap and so on. I like the user management interface in jira much more than in crowd. Does the jira internal user server support the same SOAP protocol like crowd to support external applications like Hudson or Jenkins. Any hints on that are welcome.

Regards

Chris

[Jobin Kuruvilla [Adaptavist] · Accepted solution]

Yes, you can get the users/groups etc from JIRA using remote API. However one thing that is missing will be SSO. There could be other features but sounds like your config is pretty straight forward.

[MatthewC]

I know it's an old question but..... Jobin is rigth with his answer but I'd like to add a few exceptions.

If you are a standard Jira user, there is no reason to buy Crowd any more. If you already have Crowd, it's dubious if it's worth even renewing.

The only use cases I can see where it might be worth keeping it are:

• If SSO is important to you (multiple Atlassian apps, no NTLM/Kerberos login)
• Crowd can be clustered giving some form of relience. Jira still can't do clustering (and probably never will) but you can do a cold stand by server but it's still going to blip.
• You want to seperate your user account creations (crowd-administrators) from your application administrators (jira-administrators). Sometimes you may have a situtaion where only the security team are allowed to create accounts.

These really are edge cases and not your usual install.