You need to sign in to do that
Don't have an account?
Eleanor Stanley
AADSTS650056: Misconfigured application when setting up SSO with Azure AD
While working with our IT team to set up Microsoft SSO for Salesforce we have encountered the error: Message: AADSTS650056: Misconfigured application.
We have read and worked through: https://docs.microsoft.com/en-us/troubleshoot/azure/active-directory/error-code-aadsts650056-misconfigured-app but the error is still in place.
I offer the following information/request more information to resolve the ongoing issue:
> The client has not listed any permissions for 'AAD Graph' in the requested permissions in the client's application registration.
Eagle: How do we check this for SF?
> Or, the admin has not consented in the tenant.
Eagle: This is not relevant for a manually configured SSO, but if it is where do we find the settings
> Or, check the application identifier in the request to ensure it matches the configured client application identifier.
Eagle: Double checked the issuer details and they are correct (meta file was automatically created from the file, not manually entered)
> Or, check the certificate in the request to ensure it's valid.
Eagle: Meta file was automatically created from the file, not manually entered, so there are no issues with the certificate
Any help would be appreciated!
We have read and worked through: https://docs.microsoft.com/en-us/troubleshoot/azure/active-directory/error-code-aadsts650056-misconfigured-app but the error is still in place.
I offer the following information/request more information to resolve the ongoing issue:
> The client has not listed any permissions for 'AAD Graph' in the requested permissions in the client's application registration.
Eagle: How do we check this for SF?
> Or, the admin has not consented in the tenant.
Eagle: This is not relevant for a manually configured SSO, but if it is where do we find the settings
> Or, check the application identifier in the request to ensure it matches the configured client application identifier.
Eagle: Double checked the issuer details and they are correct (meta file was automatically created from the file, not manually entered)
> Or, check the certificate in the request to ensure it's valid.
Eagle: Meta file was automatically created from the file, not manually entered, so there are no issues with the certificate
Any help would be appreciated!
Desland Vando
Any good Soul with a possible solution?!! We are having the same problem.