Introduction
This article is helpful for resolving common errors encountered while configuring SAML when integrating JFrog Cloud instances with Azure Active Directory (AD), particularly in scenarios involving a CNAME.
Error message
AADSTS700016: Application with identifier 'https://<your_instance>.jfrog.io' was not found in the directory 'xyz'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant.
Attaching the screenshot of the error:
Resolution
This error typically indicates that Azure AD is expecting the request to come from the CNAME, but the configured Identifier (Entity ID) in the Azure AD application might not match the URL used in the SAML request, or only the default JFrog URL is listed or vice versa.
To address the error mentioned, follow these resolution steps:
Step 1: Verify Configuration
Refer to the Official Documentation: Ensure that all SAML configuration steps have been followed as outlined in the official JFrog documentation: JFrog SAML SSO Configuration with Azure AD .
Step 2: Update Azure Configuration
Add URLs in Azure AD: In your Azure Active Directory settings for JFrog, add both your CNAME and the default JFrog URL to the application's SAML configuration.
Example of URLs to be configured:
CNAME: https://abc.com
Default URL: https://<your_instance>.jfrog.io
Attaching the screenshot for reference
If the issue persists after following the steps above, please reach out to JFrog support for further assistance and debugging.
Conclusion
The most frequent cause of the AADSTS700016 error during JFrog Cloud SAML configuration with a CNAME is the omission of one of the hostnames in the Azure AD application's Identifier (Entity ID) list. By including both the default JFrog URL and your custom CNAME URL as valid identifiers, you should successfully resolve this application not found error.