Hello @marcelina.barycka !
Thank you very much for the suggestions.
To be able to test the suggestions, I first need to redirect users to a personalized page using what you suggest about “Custom error pages”, as this is where I can redirect users to the flow of “https://auth.acme.com/authorize?client_id=xxxx” depending on their organization.
My error page is: https://auth.linkedin.acme.com/error
But unfortunately, when users are redirected to that page, the URL parameters do not contain any relevant information.
https://auth.linkedin.acme.com/error?client_id=&connection=&lang=en&error=invalid_request&error_description=You may have pressed the back button, refreshed during login, opened too many login dialogs, or there is some issue with cookies, since we couldn’t find your session. Try logging in again from the application and if the problem persists please contact the administrator.&tracking=e40e9ddxxxxx355a2bd
I tried checking the headers and cookies, but I still can’t find anything that tells me which organization it belongs to.
The referer is Linkedin.com, so I have no way of knowing where it comes from.
Even though I can redirect people to an error page, I have no way of building the URL in https://auth.acme.com/authorize?client_id=xxxx
So I have reached a dead end that only depends on Auth0.
I feel that this feature of being able to redirect a user in case of login error is essential for the proper functioning of organizations.
And this was LinkedIn’s response; they clearly aren’t going to do anything on their end. It is basic functionality to be able to disable the login button once it has been pressed.
Honestly, I don’t want to migrate to another authentication provider, but if I can’t find a solution to this problem, I will have no other option.
Thank you for your time and I hope you can help me solve this problem.