26 articles tagged Authorization.
This post was originally published as “White Paper: OpenID Connect (Authorization Code Flow) with Red Hat SSO” on the Levvel Blog.
Read article: OpenID Connect (Authorization Code Flow) with Red Hat SSOA while back I needed a summary of which protocols were supported/recommended in different situations by Azure Active Directory while I was researching the “When To Use Which (OAuth2) Grants and (OIDC) Flows” post. So, I am summarizing it here.
Read article: Summary of Azure Active Directory OAuth2 Authorization Grant and OIDC Authentication Flow UsesIn part 1 and part 2 of Understanding OpenID Connect, core concepts and the first Authentication Flow (Authorization Code Grant Flow) were introduced. In part 3, we look at the remaining Authentication Flows (Implicit Flow and Hybrid Flow) and some other features of the OIDC specification.
Read article: SAML2 vs JWT: Understanding OpenID Connect Part 3This post continues our discussion of OpenID Connect (OIDC). We look at one of the three Authentication Flows defined by the OIDC spec — the Authorization Code Grant Flow.
Read article: SAML2 vs JWT: Understanding OpenID Connect Part 2I was recently involved in a conversation where someone asked the question what is FGA (Fine Grained Authorization) versus Coarse Grained Authorization(CGA)? From their perspective, there was just authorization. Further distinction was not needed.
Read article: Fine Grained Authorization versus Coarse Grained AuthorizationI generally recommend to clients that DataPower RBM (Role-Based Management) be configured to perform authentication and authorization of DataPower administrators and developers with LDAP. In particular, whatever respository serves as the central repository of user information should be used (of…
Read article: RBM–Administrative Access & Security for DataPower
