@RutJWhalen 

Please check whether the relevent URI are added to "Native" application type under App registrations for the mentioned instance in Azure AD.

This could be an invalid Azure AD configuration. Some related documentation links are given below so you can check the configuration:

https://docs.ifs.com/techdocs/foundation1/040_administration/210_security/015_authentication/020_configure_azure_ad/default.htm

https://docs.ifs.com/techdocs/foundation1/020_installation/400_installation_options/030_touch_apps/010_touch_apps_server/35_open_id_connect/default.htm

Also please check the Redirect URIs for these Apps as documented here:

https://docs.ifs.com/techdocs/Foundation1/040_administration/415_touch_apps/090_touch_apps/10_account_manager/default.htm

https://docs.ifs.com/techdocs/Foundation1/020_installation/400_installation_options/130_add-on_cmp/mwo/default.htm#Applying_the_Redirect_URI

@James Ashmore / @Darshana Herath 

The customer is still experiencing issues.

We have been asked for the Tenant ID, Client ID (Web)/Client ID (Native) and the Client Secret.

The customer has advised that they cannot see this value and would have to create another Secret value, however, they have queried what impact this will have, i.e. will it affect other areas.  It is the Sandbox we are test and having issues with. 

Currently, my colleagues cannot access the Sandbox and cannot use the TAS MWO Maintenance 10.   I believe that creating a new Secret should not impact anything else, can you please clarify.

Thanking you.

John

I understand that if a new Client Secret is created then it would need configuring in the Admin Console.

@RutJWhalen it sounds like more support is required. Please raise a support ticket so we can support the customer in this process

Cheers

James

@James Ashmore @Darshana Herath 

Thank you both for your advice.

After generating a new client secret and updating the configuration in the Admin Console my colleagues were able to access the environment again using SSO.  However, the MWO Mobile application again reported a reply url issue.   It turns out that there was a trailing / in the system URL and once this was removed the mobile application connected without any issues.