-
Notifications
You must be signed in to change notification settings - Fork 839
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
UpdatePasswordCredentials no longer works #5222
Comments
Thanks for reporting this issue! We'll get this routed to the correct team for further investigation. |
Hi @kurtzeborn, has there been any update on this front that you can share? |
Any news about this issue? We are having the same problem trying to create a secret to use with HPA in AKS. |
Is there any updates or workarounds for this? This is currently preventing us from using Terraform to automate our AKS cluster deployments as we can't create a client secret for the SPN. |
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @dkershaw10, @baywet. |
Thanks please this is super important! |
Azure AD Graph API is now deprecated. We do not support SDK fixes to this product anymore. Please refer to this issue for additional way to get support to move to Microsoft Graph API: |
Bug Report
services/graphrbac/1.6/graphrbac
UpdatePasswordCredentials
v29.0.0
,v31.1.0
What happened?
UpdatePasswordCredentials
successfully creates (or updates) a credential attached to a service principal and the API can retrieve it after creating it. This credential does not appear to work with AKS, nor does it appear in the UI after creating it.What did you expect or want to happen?
The credential should appear in the UI or manifest of the service principal after creating the object.
How can we reproduce it?
Create a mutate a service principal's credentials with
UpdatePasswordCredentials
, and attempt to use the service principal (which will result in an error that the credential is not working) or check the Azure UI (which will exclude the new / updated credential).Possible Cause.
I believe this might be caused by the migration from Azure AD Graph 1.6 to Microsoft Graph 1.0. Credentials created in the UI have a different schema than the ones created by
UpdatePasswordCredentials
.Anything we should know about your environment.
This issue was first reported in the Azure AD Terraform Provider: hashicorp/terraform-provider-azuread#66
The text was updated successfully, but these errors were encountered: