Active Directory Dashboard doesn't respect OU/Container DN setting
Active Directory Dashboard doesn't respect OU/Container DN setting
I might be misunderstanding how the setting is meant to work, but when I have an Active Directory Dashboard entry, and configure the "OU/Container DN" setting, the dashboard still opens at the root of the domain.
I'd like to have it set to open at a sub-OU so that we can let our team have access to manage user accounts, but not give them the whole directory tree to view.
We're running RDM version 2023.2.18.0 if that helps!
All Comments (9)
Hello Stephen02,
This appears to be a bug with our new Active Directory dashboard, it's currently ignoring the OU entered into the Entry. I will log a ticket and fix it in the next RDM build.
Thanks for pointing out this issue, please let me know if you have any other questions or feedback on the new Active Directory Dashboard.
Regards,
Paul
It would be great if the secure gateway (SSH Tunnel) would work with the Active Directory Dashboard session type too - it would mean we wouldn't have to give direct access to the domain controllers to our support team.
Oh, and one other thing I've noticed - the Active Directory Dashboard expects the credentials to be in the form DOMAIN\user.name, so if we have our credentials stored with the domain name and username in the separate fields, it doesn't work. I guess it should accept either approach?
Oh, and one other thing I've noticed - the Active Directory Dashboard expects the credentials to be in the form DOMAIN\user.name, so if we have our credentials stored with the domain name and username in the separate fields, it doesn't work. I guess it should accept either approach?
You are correct either approach should work, I think that this issue may be fixed already in our next build which has not yet been released publicly. Please let me know if the next build still exhibits this issue.
It would be great if the secure gateway (SSH Tunnel) would work with the Active Directory Dashboard session type too - it would mean we wouldn't have to give direct access to the domain controllers to our support team.
Yes I agree this would also be great, I will log a ticket to add this support.
Oh, and one other thing I've noticed - the Active Directory Dashboard expects the credentials to be in the form DOMAIN\user.name, so if we have our credentials stored with the domain name and username in the separate fields, it doesn't work. I guess it should accept either approach?
You are correct either approach should work, I think that this issue may be fixed already in our next build which has not yet been released publicly. Please let me know if the next build still exhibits this issue.
We're now running 2023.2.22.0 and it the AD Dashboard still requires the credentials to be stored in the DOMAIN\user.name format. We're using a lookup to the user's private vault, in case that makes any difference.
Thanks we will log a ticket and look into the issue for our next patch release.
Paul
Hello,
The fix for the AD Dashboard entry to respect the OU/Container setting is now available in the latest RDM 2023.2.22.
Let us know if that works on your end.
Best regards,
Érica Poirier
The fix for the AD Dashboard entry to respect the OU/Container setting is now available in the latest RDM 2023.2.22.
Let us know if that works on your end.
Sorry for the late response - yes, that sorted it - thanks!