When issuing an Access Token during the Implicit Grant, the Authorization Server does not authenticate the OAuth Client. Although in some cases, the OAuth Client identity can be verified via the redirect_uri used to deliver the Access Token to the OAuth Client. The Access Token may be exposed to the Resource Owner or other applications with access to the Resource Owner's user-agent.
Implicit Grants improve the responsiveness and efficiency of some clients (such as a client implemented as an in-browser application), since it reduces the number of round trips required to obtain an Access Token. However, this convenience should be weighed against the security implications of using Implicit Grants, such as those described in OAuth 2.0 Sections 10.3 and 10.16, especially when the Authorization Code Grant Type is available.
Implicit Grant is the Grant Type for the Implicit Grant which would typically be used with a OAuth Public Client as is often encountered in Mobile Apps where the OAuth Client can NOT be trusted with Credentials.
Since this is a redirection-based Grant Type, the OAuth Client must be capable of interacting with the Resource Owner's User-agent (typically a web browser) and capable of receiving incoming requests (via redirection) from the Authorization Server.
The Implicit Grant type does not include OAuth Client authentication, and relies on the presence of the Resource Owner and the registration of the redirection URI. Because the Access Token is encoded into the redirection URI, the Access Token may be exposed to the Resource Owner and other applications residing on the same device.
+----------+ | Resource | | Owner | | | +----------+ ^ | (B) +----|-----+ Client Identifier +---------------+ | -+----(A)-- & Redirection URI --->| | | User- | | Authorization | | Agent -|----(B)-- User authenticates -->| Server | | | | | | |<---(C)--- Redirection URI ----<| | | | with Access Token +---------------+ | | in Fragment | | +---------------+ | |----(D)--- Redirection URI ---->| Web-Hosted | | | without Fragment | Client | | | | Resource | | (F) |<---(E)------- Script ---------<| | | | +---------------+ +-|--------+ | | (A) (G) Access Token | | ^ v +---------+ | | | Client | | | +---------+
(A) #The client initiates the flow by directing the resource owner's User-agent to the Authorization_endpoint. The client includes:
- requested OAuth Scopes
- local state
- redirect_uri - to which the authorization server will send the User-agent back once access is granted (or denied).
(B)#The Authorization Server authenticates the Resource Owner (via the User-agent) and establishes whether the Resource Owner grants or denies the client's access request.
(C)#Assuming the Resource Owner grants access, the Authorization Server redirects the User-agent back to the client using the Redirect URI provided earlier. The Authorization Response includes:
- Access Token in the URI fragment
(D)#The User-agent follows the redirection instructions by making a request to the OAuth Client (which does not include the fragment per RFC 2616). The User-agent retains the fragment information locally.
(E)#The web-hosted OAuth Client resource returns a web page (typically an HTML document with an embedded script) capable of accessing the full Redirect URI including the fragment retained by the User-agent, and extracting the Access Token (and other parameters) contained in the fragment.
(F)#The User-agent executes the script provided by the web-hosted client resource locally, which extracts the Access Token.
(G)#The User-agent passes the Access Token to the OAuth Client. Security Considerations comes when you realize that unlike with a remote server URL, there is no reliable way to ensure that the binding between a given redirect_uri and a specific Mobile Device application is honored. Any application on the Mobile Device can become a Man-In-The-Middle attacker in the redirection process and cause it to serve the redirect_uri.
Unlike when using the Authorization Code Grant the you can only use the Authorization Code if you have access to the client’s credentials this is what saves web applications from impersonating each other: the Client Secret is stored on the Website and NOT on the browser.
More Information#There might be more information for this subject on one of the following:
- Encoding claims in the OAuth 2 state parameter using a JWT
- Federation Assurance Level
- Grant Types
- Hybrid Flow
- Implicit Flow
- Implicit Grant
- OAuth 2.0 Use Cases
- OAuth 2.0 Vulnerabilities
- OAuth Security Topics
- OpenAM Endpoints
- OpenID Connect Flows
- Refresh Token