Skip to content
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

ADManagedServiceAccount: KeberosEncryptionType doesn't work on creation #650

Open
Erwan-loot opened this issue Apr 7, 2021 · 1 comment · May be fixed by #722
Open

ADManagedServiceAccount: KeberosEncryptionType doesn't work on creation #650

Erwan-loot opened this issue Apr 7, 2021 · 1 comment · May be fixed by #722
Labels
bug The issue is a bug. help wanted The issue is up for grabs for anyone in the community.

Comments

@Erwan-loot
Copy link

Exemple if you create a account with KerberosEncryptionType = AES256
The creation of a GMSA account let the parameter "KerberosEncryptionType" in {RC4, AES128, AES256} (Default behavior when you let this paramter empty)
When you reapply a second time while the account is already created the parameter is changed correctly to AES256

Add the parameter kerberosencryptiontype in the creation as the CMDLET

new-adserviceaccount -kerberosencryptiontype

@johlju johlju changed the title [ADManagedServiceAccount]KeberosEncryptionType doesn't work on creation ADManagedServiceAccount: KeberosEncryptionType doesn't work on creation Apr 10, 2021
@johlju johlju added bug The issue is a bug. help wanted The issue is up for grabs for anyone in the community. labels Apr 10, 2021
@dasy77
Copy link

dasy77 commented Feb 15, 2025

Almost 4 years have now passed and the bug has still not been fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue is a bug. help wanted The issue is up for grabs for anyone in the community.
Projects
None yet
3 participants