Issue while setting up SAML 2.0 with Azure AD
search cancel

Issue while setting up SAML 2.0 with Azure AD


Article ID: 243279


Updated On:


Clarity PPM On Premise


Error -  AADSTS700016: Application with identifier 'https://*******/niku/nu/sso/BroadcomS' was not found in the directory '*******'. 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.


Release : 16.0.1

Component : Clarity Security Integration


This is caused by Entity ID mismatch between Clarity and Azure.


  1. When importing metadata to clarity using the import option you are asked for a Configuration ID. The entity ID which clarity automatically generates is based on this ID.
    Ex:- If you mention Configuration ID as "AzureSSO" then the Entity ID which gets inserted into SAML Configurations is built as http(s)://%hostname%/niku/nu/sso/AzureSSO. 

  2. Since the metadata doesn't contain the Service Provider Entity ID which is mentioned on Azure side you need update this manually after the import is complete.

  3. Configure the Column "Entity ID" from New UX -> Administration -> Authentication and Keys -> SAML Configurations.

  4. Modify this value and configure the value that's configured on the Azure Side.

Note :- the error might be different for Various IDP's but this needs to be a general check that you need to perform after configuring SAML with Clarity.