-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Credential objects missing CustomKeyIdentifier property, causes issues #6219
Comments
@darshanhs90 Hey Haridarshan, would you happen to know why the above scenario is disallowed? I am able to reproduce the above exception, but am unsure why the server would return a |
@darshanhs90 gentle ping |
@RBACAsk ping on the question above 😀 |
Another repro of this issue can be found here: #6784 |
Remove-AzureRmADAppCredential throws the same error when trying to remove key credential from an app that has multiple credentials. |
Does anyone have any workarounds other than the AzureAD module or a fix estimate? This has disappointingly broken my automated certificate renewal script. |
I see no Chance to deploy dynamics365 on-prem without this step? New-AzureRmADSpCredential -ObjectId CertValue -EndDate "04.09.2019 10:24:08" -StartDate "04.09.2018 10:04:08" and the same result: |
@y325A Did you ever find a work around? I am in the same boat as you. |
@alex-moffitt The newer powershell release should have the fix for this issue.Since @grlin fixed the issue some time back |
@darshanhs90 or @grlin I might be doing it wrong then. I am on 6.13.1
|
@alex-moffitt The fix is in the new Az 1.0 release. |
@grlin For AzureRM PowerShell users, which module/library should we update to get the fix? |
Any version of Az after 1.0 should include the fix. AzureRM is no longer being updated. |
@grlin Thanks. I didn't realize Az is actually a package. |
@grlin I'm attempting to use this new api, but I'm failing with a new error. It appears that we fail to retrieve the application from graph and receive a 404. I can open a new issue if you'd like:
|
Hi @masisley I think this is a separate issue. |
Hi,
I've determined that the PSADPasswordCredential and PSADKeyCredential objects defined in the object data model are missing the "CustomKeyIdentifier" property. This issue will typically not be seen if creating the objects and credentials exclusively through Azure PowerShell as the CustomKeyIdentifer property will never be populated. However, this missing property can cause issues when managing credentials on an application or service principal where one of the existing credentials in the object has a non-null value for this property. The typical error message looks like:
New-AzureRmADAppCredential : Update to existing credential with KeyId 'xxx' is not allowed.
Repro Steps:
The text was updated successfully, but these errors were encountered: