Method-specific configuration tips Both client information to be pre-configured in an Authlete service, and tasks to be done by an authorization server on receiving an token request, are different for each client authentication method.
Difference between 1.1 and 2.0 (and later) Authlete 1.1 Authlete 2.0 and later Verification policy When client secret is included in a token request, Authlete always verifies its value regardless of configuration i.e. it ignores settings for client type and client authentication method.
Authlete settings You don't have to configure any additional settings because Authlete automatically generates and manages the client's ID and secret, which are required for this client authentication method.
Authlete の設定 このクライアント認証方式に必要となるクライアント ID とクライアントシークレットは、Authlete が自動的に生成・管理するため、Authlete への追加設定は不要です。
Client Types) is "confidential", at least one client authentication method except NONE must be supported.
This client authentication method is mentioned in RFC 6749.
この方式は RFC 6749 で言及されています。
In this case the client authentication method is completely managed by PostgreSQL.
この場合、クライアントの認証方式は PostgreSQL に完全に任されます。
Conținut posibil inadecvat
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.