OAuth handles authorization: deciding whether a user may access a requested resource. It can work alongside OpenID Connect (OIDC), which handles authentication—proving who the user is. For example, a page restricted to administrators requires a permission check, not just a successful login. section 8.1
In single sign-on, a shared identity provider (IdP) supports access across protected applications. The flow obtains an access token after valid credentials are supplied and maintains the session by refreshing the token. OAuth's role in that flow is authorization; it is not the login mechanism. section 8.1 section 8.6
Online-shop access
An online shop needs to know who placed an order and protect accounts from impersonation and payment-card misuse. A Keycloak container acts as the IdP. Once the UI is authenticated, it can pass credentials and permission information to a backend API in a JWT; authorization determines whether access to a requested resource is permitted. section 8.1 section 8.6








