Overview#

When a OAuth Client registers with an Authorization Server the OAuth Client must provide a Redirect_uri.

The Redirect_uri is used when a Resource Owner grants Authorization to the OAuth Client. Following the successful Authorization by the Resource Owner at the Authorization Server for the OAuth Client for Resource Server the Resource Owner is redirected back to the OAuth Client's Redirect_uri.

More Information#

There might be more information for this subject on one of the following:

• Access Token Request
• Application_type
• Authorization Code Flow
• Authorization Request
• Authorization Request Parameters
• Authorization Response
• Best Practices OpenID Connect
• Claimed Https Scheme URI Redirection
• Covert Redirect Vulnerability
• Creating an OAuth 2.0 Client Application
• Custom URI scheme
• Encoding claims in the OAuth 2 state parameter using a JWT
• Explicit Endpoint
• Form Post Response Mode
• Fragment Response Mode
• Identity Token
• Implicit Flow
• Implicit Grant
• Invalid_grant
• OAuth 2.0 Client Registration
• OAuth 2.0 Endpoints
• OAuth 2.0 JWT Secured Authorization Request
• OAuth 2.0 Security Best Current Practice
• OAuth Dynamic Client Registration Metadata
• OAuth Error
• OAuth Parameters Registry
• OAuth Token Response
• OpenID Connect
• OpenID Connect Authentication Response
• OpenID Connect Front-Channel Logout
• Private-Use URI Scheme Redirection
• Query Response Mode
• Response_mode
• Response_type
• Web Blog_blogentry_101017_1
• Web Blog_blogentry_140615_1
• Web Blog_blogentry_150617_1
• Web Blog_blogentry_160615_1