1

I am attempting to setup an Azure AD application to authenticate using a certificate. I have been using this guide to successfully set this up after failing following this guide.

I wish to now automate the process so it can be added to our general build scripts, looking at the docs for the New-AzureADApplication command it includes a parameter set(ApplicationWithKeyCredentialParameterSet) that takes a PSADKeyCredential. using this to create an application and then downloading the metadata gives me the following

"keyCredentials": [
{
  "customKeyIdentifier": null,
  "endDate": "2015-12-31T11:00:00Z",
  "keyId": "586b4d3e-84cf-43ec-a913-a33ef5075fdc",
  "startDate": "2004-12-31T12:00:00Z",
  "type": "AsymmetricX509Cert",
  "usage": "Verify",
  "value": null
}

]

If I use the ApplicationWithKeyPlainParameterSet I get the same result. Does anyone know why I am getting a null Value field? If there is a different way I should be setting up the certificates I'm open to changing my process.

1 Answer 1

1

The 'value' field for the key credentials is always returned as 'null' for applications and service principals.

Sign up to request clarification or add additional context in comments.

1 Comment

You're correct, despite the metadata returning null for the 'value' the credentials are added successfully.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.