Hi @Vyhmeister, Ronald ,
The app registration being targeted by the SAML AuthN Request from your App to Azure AD B2C is found by looking through your App Registrations to find an App Registration that has a matching identifierURI to the issuerURI in the AuthNRequest. There cannot be any missing slashes, extra spaces, or other differences.
Then Azure AD B2C looks at the metadata URL that is configured in the manifest of this App Registration, and checks the AssertionConsumerURL
inside the metadata document, to check if the ACS in the SAML AuthN request has the same value. I do not see the AssertionConsumerURL
listed in your metadata. If the application's metadata AssertionConsumerService
element is missing, or you want to override it, you need to configure the application registration manifest replyUrlsWithType
property.
"replyUrlsWithType":[
{
"url":"https://samltestapp2.azurewebsites.net/SP/AssertionConsumer",
"type":"Web"
}
],
Let me know if this helps and if you have further questions. Feel free to share app registration screenshots if you still face any issues.
If the information helped you, please Accept the answer. This will help us as well as others in the community who may be researching similar issues.