Repository navigation
no way to unlink account/domain from ldap聽#3685
Description
(localcloud) SBCM5> > link domaintoldap domainid=5a155ee3-70dd-4549-9d29-4c926530a8f0 type=group ldapdomain=cn=admins,ou=groups,dc=acs,dc=echt,dc=net accounttype=2
馃檲 Error: (HTTP 530, error code 9999) Entity already exists:
User is able to link domain/account to LDAP but there's no way to remove this link if not deleting it in DB.
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
yadvr commentedon Aug 12, 2020
cc @DaanHoogland any remarks?
DaanHoogland commentedon Sep 18, 2020
@rhtyd @borisstoyanov I remember working on a similar issue for marcus or ilya. Can you revalidate @borisstoyanov can you check on latest and add some details?
DaanHoogland commentedon Nov 24, 2020
@borisstoyanov, the idea is that you would delete an account if you no longer want the link. What is the idea of unlinking? what would the value of the account and the users in it if there is no ldap linked?
nvazquez commentedon Aug 10, 2021
@DaanHoogland @borisstoyanov any update on this?
DaanHoogland commentedon Aug 11, 2021
no update, what is the use of a unlinked domain or account? it would be filled with autoimported/autosynced users from ldap. Why would you want to keep those?
nvazquez commentedon Aug 11, 2021
In my opinion unlinking a domain or account should remove access to CloudStack from LDAP accounts, what about removing those accounts' information from DB?
DaanHoogland commentedon Aug 12, 2021
isn't removing the account/domain good enough? what is the added value of unlink?
borisstoyanov commentedon Aug 12, 2021
if the account was created before it was linked then it should remain without the possibility to authenticate to LDAP server but native only auth. if any user was created when it was linked it should be disabled the least if not removed
19 remaining items