Jump to content

SSO Setup - Different Tenant


GSM
 Share

Recommended Posts

Hi there,

We are trying to get one our international teams setup with SSO who are on a different domain and tenant on our instance. We've setup the Hornbill app on their tenant as we did for the UK, set it up all correctly on Hornbill. 

When you use the drop-down menu on the SSO screen and select the correct SSO profile and attempt to login as a user from that domain we get.

Sign in

Sorry, but we’re having trouble signing you in.

 
AADSTS700016: Application with identifier 'https://sso.hornbill.com/*****/live' was not found in the directory '9c4e83f8-03c5-442d-8cf3-*******'. 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.
 
Settings on the app are as the same as the UK.
 
Any ideas anyone?
 
 

 

 

Capture.JPG

Link to comment
Share on other sites

  • GSM changed the title to SSO Setup - Different Tenant
41 minutes ago, GSM said:

Hi there,

We are trying to get one our international teams setup with SSO who are on a different domain and tenant on our instance. We've setup the Hornbill app on their tenant as we did for the UK, set it up all correctly on Hornbill. 

When you use the drop-down menu on the SSO screen and select the correct SSO profile and attempt to login as a user from that domain we get.

Sign in

Sorry, but we’re having trouble signing you in.

 
AADSTS700016: Application with identifier 'https://sso.hornbill.com/*****/live' was not found in the directory '9c4e83f8-03c5-442d-8cf3-*******'. 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.
 
Settings on the app are as the same as the UK.
 
Any ideas anyone?
 
 

 

 

Capture.JPG

Why would this need adding in, when it's not needed for the UK tenant?

 

 

sd.JPG

Link to comment
Share on other sites

Ok using Azure's fix it option and by adding additional URLs this is now working.

Doesn't make any sense to me as the UK one apart from having a wildcard in the reply URL, the entity ID is completely different

1st pic is the international tenant, second is UK.

Anyone care to shed any light, FYI you it doesn't accept wildcards in the URL anymore, the last time i got around this by editing the manifest but this doesn't appear to work anymore./

Capture2.JPG

UK.JPG

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...