You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Daan Hoogland (JIRA)" <ji...@apache.org> on 2017/02/08 09:24:00 UTC
[jira] [Closed] (CLOUDSTACK-1477) Per-domain or Per-account LDAP
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daan Hoogland closed CLOUDSTACK-1477.
-------------------------------------
Resolution: Won't Fix
> Per-domain or Per-account LDAP
> ------------------------------
>
> Key: CLOUDSTACK-1477
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1477
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: API, UI
> Affects Versions: Future
> Environment: CloudStack & LDAP
> Reporter: Clayton Weise
> Priority: Minor
> Labels: account, authentication, domain, features, ldap, password, suggestion, user
> Original Estimate: 672h
> Remaining Estimate: 672h
>
> Currently LDAP only allows for a global config. Individual domains may have their own LDAP servers for authentication. VMware vCloud Director supports the ability for each domain to have a separate LDAP server and I would like to put this feature up to a vote to expand the existing LDAP authentication from a global config to per-domain or per-account (based on what the community feels is most appropriate).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)