Basically, in comparison with part 1, the Openstack authentication against the Keystone server is now achieved by OpenAM itself, thanks to a specialized authentication module.
Our belgium partners Paradigmo ( ) enhanced the previous solution exposed in part 1.
This authentication module is also responsible for storing the Keystone token in the user’s OpenAM session, so that it can be later retrieved by the J2EE agent running in the OpenIG web container.
Yet, OpenIG remains, to add keystone tokens to client requests on the fly.
This architecture leverages OpenAM authentication framework and API’s and also benefits from OpenAM session failover feature if enabled. It also makes it easier to store and retrieve Keystone tokens than if it’d been implemented on the OpenIG side.
The diagram below depicts OpenIG internals …
- How to use G Suite as an external identity provider for AWS SSO - 8 juillet 2020
- Bash Oauth2/OpenID Connect wrapper - 26 mai 2020
- Webinaire “Autoriser les accès à mon API à des services tiers” avec Keycloak - 16 avril 2020