Any updates ?
Please provide an answer at the earliest as it's holding our upgrades big time.
Thank you in advance.
AuthenticationFailedException: ManagedIdentityCredential authentication failed: Managed Identity response was not in the expected format.
This is the issue we are getting as we are hosted in AWS. We need to know how to pass the Azure Client ID and Client Secret to Azure to authenticate and get token and access the KeyVault.
This is a breaking change for systems which are hosted in non-azure environments and we need more documentation around this change.
I am hosting my application in AWS. I am not sure how this will work. i went through the article but it doesnt say anything about how an external app hosted oitside azure will.authenticate using thenew azureRBAC . please provide some details.
I am also using the Angular and .NET Core version. I believe i was the first one in the forum who asked for the Elsa integration and its been quite sometime.
I followed the MVC integration and things have changed since the project was created I ran in one particular issue:
Register(typeof(Elsa.Server.Api.Endpoints.WebhookDefinitions.List).GetAssembly());
They have most likely changed the namespaces, and ran into several issues while integrating the Angular by following the above mentioned methid, especially the file path which was exceeding the length supported by window.
I highly recommend please have one documentation using the latest Elsa for Angular that would be a great help.
Thank You @jeffmh, it worked
Tried it didn't work. Please note the same token works on our previous versions of ANZ.
Below is the payload in the token :
{ "sub": "xxxxxxx", "name": "abc def", "locale": "cc", "ver": 1, "iss": "https://xys-dev.okta.com/oauth2/ausa4encmPghJQMuN356", "aud": "0oa99tynzwx1ZXFJh357", "iat": 1649879201, "exp": 1649882801, "jti": "ID.SfWV1w9rd7vXQiNUdfgUX3bJ7Jr5YsPuqYiL-vKcs", "amr": [ "pwd" ], "idp": "0oaabbuk8OMuWHMsk356", "nonce": "LUlaSVdnc2pSV2k4cVhDYlhxZ053anVOSZVYeG9RMDZOSGpqeFUwNkgwbFpU", "preferred_username": "[email protected]", "given_name": "abc", "family_name": "def", "zoneinfo": "cccccs", "updated_at": 1644261243, "auth_time": 1649879200 }
@ismcagdas we need a solution for this , as it's kind of show stopper for us.
@ismcagdas any solution to my problem of the missing claim. The token clearly has the name claim in it.
I am having the same issue with Okta and someone else is also having the same issue:
I think the above error message is "name claim is missing"
