-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
join with password, OU prefix #39
Comments
Submitted pull request #40 |
Almost a year and no traction on this PR. |
Hi @acurus-puppetmaster -- if you check the PR, it was merged back on June 16th. |
But the last release you did was in 2017. so those of us who like to use the forge released version can't access any recent changes. |
Ok...thanks for clarifying. I'll try to push a new Forge release later today or tomorrow at the latest. I'll close this once the new Forge release is available. |
Excellent news, thank you. |
v2.3.0 is up now on the Forge |
When you join with a password and provide an OU to place the computer object in the format of the OU string isn't what we would normally expect when dealing with Active Directory.
The AD distinguished name begins with OU=
Which we record in Hiera as
ad_ou: 'OU=Linux,OU=ISP,OU=Internal Systems,DC=services,DC=company,DC=com'
But the module already adds the OU=
Which means the actual OU specifed in the end becomes
OU=OU=Linux,OU=ISP,OU=Internal Systems,DC=services,DC=company,DC=com
Which fails.
It would be great if this was not added as a prefix.
The text was updated successfully, but these errors were encountered: