nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Where to Deploy Crowd - Cloud or Local

Chris Wood

Say you had Confluence installed in the cloud and wanted to integrate with Crowd and an active directory LDAP at a remote site.

What is the recommended deployment for performance/security?

1) Confluence (Cloud) -> Crowd (Cloud)-> LDAP connector (ssl option) to AD (Remote)

2) Confluence (Cloud) -> Crowd (Remote) with SSL in tomcat, LDAP connector to AD (Remote)

Thank you

Accepted answers

Tiago Comasseto

Hi Chris,

Since the LDAP is remote and, even using Crowd, all password authentication requests will be forwarded to your LDAP, the performance shouldn'd be much different between both options.

Even so I would go with opition one, because in case the LDAP communication fails for any reason, the users with a valid token in Crowd will still be able to access Confluence for some time.

Cheers

All comments

Tiago Comasseto

Hi Chris,

Since the LDAP is remote and, even using Crowd, all password authentication requests will be forwarded to your LDAP, the performance shouldn'd be much different between both options.

Even so I would go with opition one, because in case the LDAP communication fails for any reason, the users with a valid token in Crowd will still be able to access Confluence for some time.

Cheers

Harry Chan5

Agrees with going with Option 1. Crowd being "local" to Confluence also means Crowd's caching of LDAP will help with performance.

Chris Wood

Thanks Tiago and Harry - will stage option 1.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

crowd

crowd-administration