ldap - Deactivate Users
We use ldap to maintain our users within cascade server with the "Orphaned LDAP Users" set to Deactivate, this works great for our purposes when they leave the ldap group, however when a user is put back into the applicable ldap group they remain "Enabled" = false. Is their a setting that exists that will automatically re-enable these users when they appear back in the ldap group?
Discussions are closed to public comments.
If you need help with Cascade CMS please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Ryan Griffith on 23 Dec, 2015 07:55 PM
Hi Eric,
Unfortunately, there isn't a way to re-activate an existing user. You can only activate new users (policy level) and choose to delete/disable/ignore orphaned users.
This does sound like an interesting feature though. I highly recommend posting a suggestion to our Idea Exchange if you would like for this feature to be considered for a future release.
I think your best bet would be to delete the users that become orphaned so that when they are re-created they are enabled, assuming your user policy is set to enable new users. The problem there is you would lose history and audit information. Also, I believe if the user still has active workflows or locked assets the deletion would not occur.
Please let me know if you have any questions.
Thanks!
2 Posted by Ryan Griffith on 30 Dec, 2015 01:36 PM
Hi Eric,
My apologies, I misread your comment; specifically when you stated the user is placed back into an applicable group in LDAP.
Speaking with the developers, the user should definitely be reenabled and un-orphaned since the LDAP account would technically be discovered again. I went ahead and logged this as a known defect and assigned it to this discussion. You can track its progress in the upper right-hand corner of this discussion; the status will change from Open to Close when it has been resolved.
Please let me know if you have any questions.
Thanks!
3 Posted by Eric on 30 Dec, 2015 08:53 PM
Thanks Ryan, I appreciate the update!
4 Posted by Ryan Griffith on 31 Dec, 2015 11:38 AM
Not a problem at all, Eric. My apologies for the inconvenience this issue may be causing you. Definitely keep an eye on the issue in the upper right-hand corner of this page or on our Release Notes.
I'm going to go ahead and close this discussion, please feel free to comment or reply to re-open if you have any additional questions.
Have a great day and Happy New Year!
Ryan Griffith closed this discussion on 31 Dec, 2015 11:38 AM.