par janua | Sep 9, 2016 | Communauté, Gestion des Identités, Sécurité, SSO
This article describes how to use authorization code grant type with OpenAM. Authorization code is the most secured grant when providing Oauth2 connection, as the access token is not stored within your browser. On openam the authorization code has been made 1H to...
par janua | Sep 9, 2016 | Communauté, Gestion des Identités, Sécurité, SSO
Refresh token lifecycle in OpenAM could be very tricky, not easy to understand and implement. So that we share in this document our experiences. 1. Description Refresh Token is a feature provided with Oauth2 Authorization code or Resource Owner Password Credentials...
par janua | Juil 15, 2016 | Communauté, Gestion des Identités, Sécurité, SSO
This post is about understanding tokens roles in OpenID Connect (OIDC) intégration: 1. Presentation OpenID Connect Specification is described at . OpenID Connect is provided on top of OAuth2 layer, defined in RFC 6749. OpenID provides authentication which is expressed...
par janua | Juin 10, 2016 | Gestion des Identités, Sécurité, SSO
This article describes how it is possible to create a new tomcat instance and deploy openam in it (which is not the default tomcat instance) very quickly. This can be very useful if you have already other openam tomcat instances. How to create and deploy a new OpenAM...
par janua | Juin 6, 2016 | Communauté, Gestion des Identités, Sécurité, SSO
OpenAM integration is tigthly coupled with Apache Server to protect web pages using a web policy agent. Apache Server can be made available out of the box when bundled with the OS, but often does not allow to be tailored to customer needs. OpenAM-compiling Apache...
par janua | Avr 14, 2016 | Communauté, Gestion des Identités, SSO
Saving OAuth2 consent: when configured as an OAuth2 service provider, OpenAM is capable of saving the user’s consent. This prevent the resource owner from having to validate the authorization consent each time for the same client and scopes. To save OAuth2...
