For example, if you are implementing the authorization code grant type, then you will require four separate OAuthV2 policies to perform authorization code generation, access code generation, access code validation, and refresh token generation.
For more information, see Implementing the authorization code grant type.
詳細については、 認可コード権限付与タイプを実装する をご覧ください。
About callback URLs If your apps require a callback URL, such as when using the OAuth 2.0 authorization code grant type (often referred to as "three-legged OAuth"), you can require developers to specify a callback URL when they register their apps.
Configuring callback URL handling If an API proxy in your API product uses "three-legged OAuth" (authorization code grant type), developers need to specify a callback URL when they register their apps.
コールバック URL の処理を構成する API プロダクトの API プロキシでThree-legged OAuth ( 認可コード権限付与タイプ)を使用する場合、開発者はアプリの登録時にコールバック URL を指定する必要があります。
Related topics Implementing the client credentials grant type Implementing the authorization code grant type API security online course (includes OAuth) OAuthV2 policy - Has lots of examples showing how to make requests to the authorization server and how to configure the OAuthV2 policy.
Requesting an access token: authorization code grant type This section explains how to request an access token using the authorization code grant type flow.
Exemplele au rolul de a te ajuta să traduci cuvinte sau expresii corect si adaptat la context. Nu sunt selectate sau validate manual, așadar pot conține termeni inadecvați. Te rugăm să raportezi exemplele pe care le consideri inadecvate. Traducerile vulgare sau colocviale sunt în general marcate cu roșu sau cu portocaliu.