Crowd access from the Internet

[Aaron Catt]

Hello,

We are wanting to utilise Crowd for SSO with Azure AD, does this application need to be placed in a DMZ for customers to access? Or does only the service desk and confluence servers need access to this Crowd application?

Many thanks

Aaron

[AnnWorley]

If you don't need users managing their own accounts in Crowd then only administrators need access to log into the Crowd console. If admins have access to browse to the server then there is no reason to make Crowd available on the internal network. The applications that use Crowd for authentication will obviously need to be able to connect to Crowd.

This may come in handy: Configuring Azure Active Directory

[Bruno Vincent]

@AnnWorley

Users couldn't make changes to their accounts here as Azure AD connector is read-only :-)

https://confluence.atlassian.com/crowd/configuring-azure-active-directory-935372375.html

"If you need to make any changes to your users, make them directly in Azure AD. You can't edit your Azure AD users in Crowd."

[AnnWorley]

Nice catch - I learn something every day on this forum! :)

[Bruno Vincent]

@AnnWorley

I guess we all do, that's the great thing about it! :-)

[Bruno Vincent]

Hi @Aaron Catt

In your use case, only your applications (JSD, Confluence etc.) will need to connect to Crowd so there's no need to place Crowd in a DMZ.

You usually place Crowd in a DMZ when users have to connect to Crowd's console to have their password reset. But since Azure AD connector is read-only it does not make much sense here.

[Lars Olav Velle]

Hi @Aaron Catt

With Kantega Single Sign-on you do not need Crowd.

Simply sync users and groups directly into the applications:

https://marketplace.atlassian.com/plugins/no.kantega.kerberosauth.kerberosauth-plugin/server/overview 

(Disclaimer: I work for Kantega Single Sign-on :) )

-Lars

[Lars Olav Velle]

If you want a demo or help setting it up, you can reach out to atlassian.support@kantega.no

Cheers!