SSO error message with mobileedge

Hi Christophe,
Did you add redirect entries for Mobile in the Astea.Identity.Server\clients.json file?
 

if that doesn’t work, do you have another environment where this is working properly?  Can you do a KDIFF or BeyondCompare on the clients.json file between those environments?  Maybe that will help to pinpoint the problem…
Thanks,
Reid

Hi Reid

Thanks for your feedback, 

we have compared between an environment on which everything is ok and the customer one and we have the same settings.

Note that we have seen that directly on the server itself if we browse to the mobile url in https://…/ we have the Microsoft login windows but when we use this url outside the VM if have this error messages.

(on the VM when we browse to the mobile server the settings is done so that when we call https:// ...: the request “stay” on the server)

It looks for us that in the customer application gateway a wrong redirection is done but as we don’t know the exact request calls between the mobile, the identity server and the azure id its difficult to validate this point.

Rgds

Christophe

Hi Christophe,

I believe this error appears after entering in the login credentials and then attempting to get redirected back to mobile to get logged in. This may be due to some invalid cookie sessions and/or cache in the browser. 

Please try to clear out the cache & cookies from the browser and try again. You can also try to use an incognito tab to see if that helps.

I hope that helps.

Best Regards,

Taz

HI Christophe,

This may not have been the case four days ago but recently we also found that Chrome once it was updated to v112 no longer allows accessing Mobile Edge as the Web SQL seems to have been completely disabled by Google now.

You should do your tests going forward with the Windows Native App client instead.  Just informing you until there is a resolution, Chrome v112 is not going to work with Mobile Edge now for the time being.