From 3d05e5be0db1e2c7af984ab5f0b6b896e2340766 Mon Sep 17 00:00:00 2001
From: LSZ
- OpenID Connect implements authentication as an extension to the - OAuth 2.0 authorization process. - Use of this extension is requested by Clients by including - the openid scope value - in the Authorization Request. - Information about the authentication performed is returned - in a JSON Web Token - (JWT) (Jones, M., Bradley, J., and N. Sakimura, “JSON Web Token (JWT),” July 2014.) + OpenID Connect在OAuth 2.0授权流程的基础上,扩展实现了认证功能. + 在客户端(Clients)发起授权请求时扩展了请求的范围(scope)值包含openid. + 认证执行返回的信息是一个JSON Web Token + (JWT) (Jones, M., Bradley, J., and N. Sakimura, “JSON Web Token (JWT),” 2014年7月.) [JWT] - called an ID Token (see Section 2 (第2节 (ID Token)). - OAuth 2.0 Authentication Servers implementing OpenID Connect - are also referred to as OpenID Providers (OPs). - OAuth 2.0 Clients using OpenID Connect - are also referred to as Relying Parties (RPs). + OAuth 2.0 认证服务端实现了 OpenID Connect 功能也被称作 OpenID 提供商 (OPs). + OAuth 2.0 客户端(Clients) 使用 OpenID Connect 功能也被称作依赖方 (RPs).