Users that go straight to the login domain get stuck #44
Description
If a user goes directly to the configured domain, like login.myapp.com without initiating the login from the app, there are no cookies set and no cryptography initiated - they get stuck in a broken cycle!
The solution is: if there's no Application/Deployment available in the ServiceLoader, this means there's no session to use correctly - but we do know the URL and have access to the database. So in this case, load the correct application from the database with the matching providerHost, then redirect the browser back to the clientHost, possibly with the clientLoginPath too.