-
Suggestion
-
Resolution: Duplicate
-
None
-
None
Medium to large companies with strict user password policies already implemented in their LDAP cannot developer to join system that do not have similar policies.
Connecting Studio to corp ldap would open the door to many developers that must comply with these policies.
[CLOUD-1889] Connect Jira Studio Users to external corporate LDAP
Ricardo DeMatos
added a comment - cast your vote.... and let's do some begging at the summit. I have a
feeling that they'd need to fix the all or nothing admin behavior of
Crowd to allow studio admins to hookup ldapd and not break the other
directories.
it us all matter of priorities, I guess.
Sent from my iPhone
On Mar 18, 2010, at 5:10 AM, "Martin van Dijken (JIRA)" <jira@studio.atlassian.com
Ricardo DeMatos
added a comment - cast your vote.... and let's do some begging at the summit. I have a
feeling that they'd need to fix the all or nothing admin behavior of
Crowd to allow studio admins to hookup ldapd and not break the other
directories.
it us all matter of priorities, I guess.
Sent from my iPhone
On Mar 18, 2010, at 5:10 AM, "Martin van Dijken (JIRA)" <jira@studio.atlassian.com
Martin van Dijken
added a comment - I am so suprised that Studio does not support this by default. Atlassian has crowd in it's portfolio, which has all that would be needed to do this and way more. Can you comment on this?
Martin van Dijken
added a comment - I am so suprised that Studio does not support this by default. Atlassian has crowd in it's portfolio, which has all that would be needed to do this and way more. Can you comment on this? 
Damian Hickey
added a comment - Would just add a comment that whatever implementation is chosen is should support open standards (i.e. SAML)
Damian Hickey
added a comment - Would just add a comment that whatever implementation is chosen is should support open standards (i.e. SAML) 
Please follow
AOD-1837for updates on this request as this issue is a duplicate.