SSO metadata file invalid

When you encounter an issue with an invalid SAML metadata file during SSO setup, there are several troubleshooting steps you can take:

1. Validate your metadata XML file using an XML validation tool (such as the W3Schools XML validator) to check for any syntax errors or formatting issues.

2. Verify that your metadata conforms to the SAML 2.0 standard specifications.

3. Ensure that all required elements are included in your metadata XML file.

4. Check if your IdP's SAML signing certificate has been recently updated. If so, you'll need to download the latest metadata file from your IdP.

5. Make sure the private key file is properly formatted as a .pem file if you're setting up an IAM identity provider.

6. Confirm that the certificate in the metadata file hasn't expired.

For Microsoft Entra ID specifically, you should:

• Locate the Federation Metadata XML in the SAML signing certificate section
• Download the certificate to ensure you have the most current version
• Then upload this fresh metadata file to your AWS service

If you continue to experience issues, clearing your browser cache or trying a private/incognito window might help, as stored data can sometimes interfere with the authentication process.
Sources
Troubleshoot Amazon Cognito - Amazon Cognito
Configure SAML 2.0 authentication in OpenSearch Service | AWS re:Post
Troubleshoot SAML federation with IAM - AWS Identity and Access Management
Invalid client provided Message when Signin in to AWS APP Studio | AWS re:Post
AWS SageMaker Unified Studio Microsoft Entra ID SAML SSO Integration Guide | AWS re:Post