You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have implemented a custom policy based on the Invite sample. An Azure function generates an invite link which is mailed to the new user. That url directs the user to our Signup policy. All the steps in the signup policy are executed successfully (user is created), but in the last step (SendClaims) we get an exception:
Which is called in the last step from the UserJourney:
<!-- Let the user fill in the signup form and create the account-->
<OrchestrationStepOrder="3"Type="ClaimsExchange">
<ClaimsExchanges>
<ClaimsExchangeId="LocalAccountSignUpWithReadOnlyEmail"TechnicalProfileReferenceId="LocalAccountSignUpWithReadOnlyEmail" />
</ClaimsExchanges>
</OrchestrationStep>
<!-- Issue an access token for the newly created account-->
<OrchestrationStepOrder="4"Type="SendClaims"CpimIssuerTechnicalProfileReferenceId="JwtIssuer" />
</OrchestrationSteps>
<ClientDefinitionReferenceId="DefaultWeb" />
</UserJourney>
The error message suggests an issue with the certificate used to sign the token, however the configuration seems ok. All certificates are in place.
Anyone encountered the same error message or can guide is in the correct direction to solve this?
The text was updated successfully, but these errors were encountered:
Did you manage to get this fixed? I've got the same problem. Following the invite flow instructions I uploaded my new cer file and issuer_secret key accordingly.
I wasn't working on solving this because of the vacation period, but the issue is still not fixed. I'm in contact with support and I'm working together with them in solving this.
I'll post something here if we find a solution.
We have implemented a custom policy based on the Invite sample. An Azure function generates an invite link which is mailed to the new user. That url directs the user to our Signup policy. All the steps in the signup policy are executed successfully (user is created), but in the last step (SendClaims) we get an exception:
This happens in the JWTIssuer TechnicalProfile from the TrustFrameworkBase policy:
Which is called in the last step from the UserJourney:
The error message suggests an issue with the certificate used to sign the token, however the configuration seems ok. All certificates are in place.
Anyone encountered the same error message or can guide is in the correct direction to solve this?
The text was updated successfully, but these errors were encountered: