A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://developer.okta.com/docs/guides/implement-grant-type/implicit/main/ below:

Implement authorization by grant type

Before you can implement authorization, you need to register your app in Okta by creating an app integration from the Admin Console.

The following sections outline the main requests required to implement the Implicit flow using direct requests to the OIDC & OAuth 2.0 API (opens new window) /authorize endpoint.

Request for tokens

This flow is similar to the Authorization Code flow, except that the response_type is token and/or id_token instead of code.

Your application redirects the user's browser to your authorization server's /authorize endpoint. If you are using the org authorization server, then your request URL would look something like this:

Note the parameters that are being passed:

See the OAuth 2.0 API reference (opens new window) for more information on these parameters.

If the user doesn't have an existing session, the request opens the Okta sign-in page. If they have an existing session, or after they authenticate, the user is redirected back to the specified redirect_uri along with a token as a hash fragment:

Your application must now extract the tokens from the URI and store them.

Validate access token

When your application passes a request with an access token, the resource server needs to validate it. See Validate access tokens.


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4