-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frodo unable to connect to improperly configured platform deployment #94
Comments
At first this looked like a total mystery to me. The UI was able to login just fine but frodo was throwing a fit. Turns out that all my Postman API calls failed, too, which made it even more suspicious. It appears that the either AM or the reverse proxy fronting AM is misconfigured and all API calls fail unless they:
For some reason, the UI is omitting the host header altogether and thus was lucky to just work. But I am pretty sure the env is heavily impaired as most API requests do include the host header by default (set automatically to the host name). In this case the AM server is configured with a different host name (am.example.com:8081) than the reverse proxy (platform.example.com:9443), causing AM to report with the following error to every authentication request:
Another issue is that the instance is using a default authentication journey in the root realm that is Frodo-incompatible (the journey has social login enabled, which frodo does not support). Frodo currently supports only simple authentication journeys using username/password and frodo supports the ID Cloud tenant admin login journey for admins with MFA disabled. |
The latest version (cli: v0.13.0, lib: v0.12.4) of frodo now allows two new parameters when adding a connection profile: --authentication-service [service] Name of the authentication service/tree to use. These parameters are currently only supported in the
After the connection profile is created with the additional parameters, the environment can be accessed as usual. In this case it requires the
|
Progress on rockcarver#73 and rockcarver#18 and resolves rockcarver#92
…ured platform deployment
Frodo Library version
Provide output of getVersion or us the CLI to get the version
frodo -v
Describe the issue
Reported by Stephen Payne on August 28:
Frodo is unable to connect to a platform instance, which is improperly configured.
The text was updated successfully, but these errors were encountered: