2024.05.10 (금)

  • 맑음속초17.3℃
  • 맑음10.6℃
  • 맑음철원11.4℃
  • 맑음동두천12.3℃
  • 맑음파주11.6℃
  • 맑음대관령9.9℃
  • 맑음춘천10.2℃
  • 맑음백령도14.5℃
  • 맑음북강릉17.1℃
  • 맑음강릉19.0℃
  • 맑음동해16.2℃
  • 박무서울13.8℃
  • 맑음인천13.4℃
  • 맑음원주12.3℃
  • 맑음울릉도15.7℃
  • 맑음수원12.0℃
  • 맑음영월9.7℃
  • 맑음충주9.6℃
  • 맑음서산12.4℃
  • 맑음울진17.4℃
  • 맑음청주13.1℃
  • 맑음대전12.4℃
  • 맑음추풍령11.1℃
  • 맑음안동11.0℃
  • 맑음상주13.9℃
  • 맑음포항17.2℃
  • 맑음군산11.1℃
  • 맑음대구11.8℃
  • 맑음전주11.3℃
  • 맑음울산15.6℃
  • 맑음창원13.2℃
  • 맑음광주12.7℃
  • 맑음부산15.4℃
  • 맑음통영13.5℃
  • 맑음목포12.6℃
  • 맑음여수15.1℃
  • 맑음흑산도13.4℃
  • 맑음완도11.9℃
  • 맑음고창9.4℃
  • 맑음순천8.1℃
  • 맑음홍성(예)11.9℃
  • 맑음8.8℃
  • 맑음제주13.7℃
  • 맑음고산13.8℃
  • 맑음성산12.0℃
  • 맑음서귀포13.9℃
  • 맑음진주9.9℃
  • 맑음강화10.5℃
  • 맑음양평11.6℃
  • 맑음이천11.3℃
  • 구름조금인제9.0℃
  • 구름조금홍천9.6℃
  • 맑음태백12.6℃
  • 맑음정선군7.8℃
  • 맑음제천8.2℃
  • 맑음보은8.4℃
  • 맑음천안8.5℃
  • 맑음보령13.1℃
  • 맑음부여9.8℃
  • 맑음금산8.0℃
  • 맑음10.8℃
  • 맑음부안11.5℃
  • 맑음임실7.4℃
  • 맑음정읍9.4℃
  • 맑음남원8.8℃
  • 맑음장수6.6℃
  • 맑음고창군9.1℃
  • 맑음영광군9.6℃
  • 맑음김해시13.9℃
  • 맑음순창군8.6℃
  • 맑음북창원14.0℃
  • 맑음양산시12.3℃
  • 맑음보성군10.6℃
  • 맑음강진군9.2℃
  • 맑음장흥8.9℃
  • 맑음해남9.3℃
  • 맑음고흥9.2℃
  • 맑음의령군10.0℃
  • 맑음함양군10.3℃
  • 맑음광양시13.6℃
  • 맑음진도군9.7℃
  • 맑음봉화8.6℃
  • 맑음영주10.6℃
  • 맑음문경12.2℃
  • 맑음청송군9.1℃
  • 맑음영덕15.4℃
  • 맑음의성8.7℃
  • 맑음구미10.8℃
  • 맑음영천14.5℃
  • 맑음경주시10.1℃
  • 맑음거창7.7℃
  • 맑음합천10.2℃
  • 맑음밀양11.4℃
  • 맑음산청9.4℃
  • 맑음거제12.2℃
  • 맑음남해13.4℃
  • 맑음11.3℃
기상청 제공
표준뉴스 로고
[기획-디지털 ID 표준] ⑮산업단체와 포럼 - 오픈ID(OpenID)
  • 해당된 기사를 공유합니다

[기획-디지털 ID 표준] ⑮산업단체와 포럼 - 오픈ID(OpenID)

Korea Digital ID(iNIS) 2(디지털 ID 산업의 발전 전략 [출처=iNIS]).jpg
▲ 디지털 ID 산업의 발전 전략 [출처=iNIS]

 

디지털 ID(Digital Identity) 분야에서 상호운용(interoperable)이 가능하고 안전한 서비스 보장을 위한 표준에 대한 수요가 증가하고 있다. 다양한 표준 조직 및 산업 기관이 활동하는 이유다.

디지털 ID 표준을 개발하는 곳은 유럽표준화기구(European Standardisation Organistions), 국제표준화기구(International Standardisation Organisations), 상업 포럼 및 컨소시엄, 국가기관 등 다양하다.

산업단체와 포럼은 공식적으로 표준화 조직으로 간주되지 않지만 디지털 ID 영역을 포함한 특정 영역에서는 사실상의 표준을 제공하고 있다.

몇몇의 경우 이들 단체들이 추가 비준을 위해 자신들이 생산한 사양을 ISO/IEC, ITU 통신 표준화 부문(ITU-T), ETSI 등 표준 기관에 제출할 수 있다.

이러한 산업단체 및 포럼에는 △인증기관브라우저 포럼(Certification Authority Browser Forum,  CA/Browser Forum) △클라우드 서명 컨소시엄(Cloud Signature Consortium, CSC) △국제자금세탁방지기구(Financial Action Task Force, FATF) △신속온라인인증(Fast Identity Online, FIDO) △국제인터넷표준화기구(Internet Engineering Task Force, IETF) △구조화 정보 표준 개발기구(오아시스)(Organization for the Advancement of Structured Information Standards, OASIS) △오픈ID(OpenID) △SOG-IS(Senior Officials Group-Information Systems Security) △W3C(World Wide Web Consortium) 등이다.

오픈ID(OpenID)는 개인 및 기업의 비영리 국제 표준화 조직으로 OpenID(개방형 표준 및 분산 인증 프로토콜)를 활성화, 홍보, 보호하기 위해 노력하고 있다.

오픈ID 코넥트 코어(OpenID Connect Core)는 핵심 OpenID 기능을 정의하고 있다. OpenID 기능은 OAuth 2.0 기반에 구축된 인증과 최종 사용자에 대한 정보를 전달하기 위한 클레임의 사용이다.

추가적인 기술 사양 문서는 검증 가능한 자격 증명 및 검증 가능한 프리젠테이션의 발급을 확장하기 위해 작성됐다. 또한 OpenID Connect 사용에 대한 보안 및 개인 정보 보호 고려 사항에 대해 설명하고 있다.

아래는 오픈ID가 발행한 'OpenID Connect Core 1.0 incorporating errata set 1' 목차 내용이다.

■ 목차(Table of Contents)

1. Introduction
1.1. Requirements Notation and Conventions
1.2. Terminology
1.3. Overview

2. ID Token

3. Authentication
3.1. Authentication using the Authorization Code Flow
3.1.1. Authorization Code Flow Steps
3.1.2. Authorization Endpoint
3.1.2.1. Authentication Request
3.1.2.2. Authentication Request Validation
3.1.2.3. Authorization Server Authenticates End-User
3.1.2.4. Authorization Server Obtains End-User Consent/Authorization
3.1.2.5. Successful Authentication Response
3.1.2.6. Authentication Error Response
3.1.2.7. Authentication Response Validation
3.1.3. Token Endpoint
3.1.3.1. Token Request
3.1.3.2. Token Request Validation
3.1.3.3. Successful Token Response
3.1.3.4. Token Error Response
3.1.3.5. Token Response Validation
3.1.3.6. ID Token
3.1.3.7. ID Token Validation
3.1.3.8. Access Token Validation
3.2. Authentication using the Implicit Flow
3.2.1. Implicit Flow Steps
3.2.2. Authorization Endpoint
3.2.2.1. Authentication Request
3.2.2.2. Authentication Request Validation
3.2.2.3. Authorization Server Authenticates End-User
3.2.2.4. Authorization Server Obtains End-User Consent/Authorization
3.2.2.5. Successful Authentication Response
3.2.2.6. Authentication Error Response
3.2.2.7. Redirect URI Fragment Handling
3.2.2.8. Authentication Response Validation
3.2.2.9. Access Token Validation
3.2.2.10. ID Token
3.2.2.11. ID Token Validation
3.3. Authentication using the Hybrid Flow
3.3.1. Hybrid Flow Steps
3.3.2. Authorization Endpoint
3.3.2.1. Authentication Request
3.3.2.2. Authentication Request Validation
3.3.2.3. Authorization Server Authenticates End-User
3.3.2.4. Authorization Server Obtains End-User Consent/Authorization
3.3.2.5. Successful Authentication Response
3.3.2.6. Authentication Error Response
3.3.2.7. Redirect URI Fragment Handling
3.3.2.8. Authentication Response Validation
3.3.2.9. Access Token Validation
3.3.2.10. Authorization Code Validation
3.3.2.11. ID Token
3.3.2.12. ID Token Validation
3.3.3. Token Endpoint
3.3.3.1. Token Request
3.3.3.2. Token Request Validation
3.3.3.3. Successful Token Response
3.3.3.4. Token Error Response
3.3.3.5. Token Response Validation
3.3.3.6. ID Token
3.3.3.7. ID Token Validation
3.3.3.8. Access Token
3.3.3.9. Access Token Validation

4. Initiating Login from a Third Party

5. Claims
5.1. Standard Claims
5.1.1. Address Claim
5.1.2. Additional Claims
5.2. Claims Languages and Scripts
5.3. UserInfo Endpoint
5.3.1. UserInfo Request
5.3.2. Successful UserInfo Response
5.3.3. UserInfo Error Response
5.3.4. UserInfo Response Validation
5.4. Requesting Claims using Scope Values
5.5. Requesting Claims using the "claims" Request Parameter
5.5.1. Individual Claims Requests
5.5.1.1. Requesting the "acr" Claim
5.5.2. Languages and Scripts for Individual Claims
5.6. Claim Types
5.6.1. Normal Claims
5.6.2. Aggregated and Distributed Claims
5.6.2.1. Example of Aggregated Claims
5.6.2.2. Example of Distributed Claims
5.7. Claim Stability and Uniqueness

6. Passing Request Parameters as JWTs
6.1. Passing a Request Object by Value
6.1.1. Request using the "request" Request Parameter
6.2. Passing a Request Object by Reference
6.2.1. URL Referencing the Request Object
6.2.2. Request using the "request_uri" Request Parameter
6.2.3. Authorization Server Fetches Request Object
6.2.4. "request_uri" Rationale
6.3. Validating JWT-Based Requests
6.3.1. Encrypted Request Object
6.3.2. Signed Request Object
6.3.3. Request Parameter Assembly and Validation

7. Self-Issued OpenID Provider
7.1. Self-Issued OpenID Provider Discovery
7.2. Self-Issued OpenID Provider Registration
7.2.1. Providing Information with the "registration" Request Parameter
7.3. Self-Issued OpenID Provider Request
7.4. Self-Issued OpenID Provider Response
7.5. Self-Issued ID Token Validation

8. Subject Identifier Types
8.1. Pairwise Identifier Algorithm

9. Client Authentication

10. Signatures and Encryption
10.1. Signing
10.1.1. Rotation of Asymmetric Signing Keys
10.2. Encryption
10.2.1. Rotation of Asymmetric Encryption Keys

11. Offline Access

12. Using Refresh Tokens
12.1. Refresh Request
12.2. Successful Refresh Response
12.3. Refresh Error Response

13. Serializations
13.1. Query String Serialization
13.2. Form Serialization
13.3. JSON Serialization

14. String Operations

15. Implementation Considerations
15.1. Mandatory to Implement Features for All OpenID Providers
15.2. Mandatory to Implement Features for Dynamic OpenID Providers
15.3. Discovery and Registration
15.4. Mandatory to Implement Features for Relying Parties
15.5. Implementation Notes
15.5.1. Authorization Code Implementation Notes
15.5.2. Nonce Implementation Notes
15.5.3. Redirect URI Fragment Handling Implementation Notes
15.6. Compatibility Notes
15.6.1. Pre-Final IETF Specifications
15.6.2. Google "iss" Value
15.7. Related Specifications and Implementer's Guides

16. Security Considerations
16.1. Request Disclosure
16.2. Server Masquerading
16.3. Token Manufacture/Modification
16.4. Access Token Disclosure
16.5. Server Response Disclosure
16.6. Server Response Repudiation
16.7. Request Repudiation
16.8. Access Token Redirect
16.9. Token Reuse
16.10. Eavesdropping or Leaking Authorization Codes (Secondary Authenticator Capture)
16.11. Token Substitution
16.12. Timing Attack
16.13. Other Crypto Related Attacks
16.14. Signing and Encryption Order
16.15. Issuer Identifier
16.16. Implicit Flow Threats
16.17. TLS Requirements
16.18. Lifetimes of Access Tokens and Refresh Tokens
16.19. Symmetric Key Entropy
16.20. Need for Signed Requests
16.21. Need for Encrypted Requests

17. Privacy Considerations
17.1. Personally Identifiable Information
17.2. Data Access Monitoring
17.3. Correlation
17.4. Offline Access

18. IANA Considerations
18.1. JSON Web Token Claims Registration
18.1.1. Registry Contents
18.2. OAuth Parameters Registration
18.2.1. Registry Contents
18.3. OAuth Extensions Error Registration
18.3.1. Registry Contents

19. References
19.1. Normative References
19.2. Informative References

Appendix A. Authorization Examples
A.1. Example using response_type=code
A.2. Example using response_type=id_token
A.3. Example using response_type=id_token token
A.4. Example using response_type=code id_token
A.5. Example using response_type=code token
A.6. Example using response_type=code id_token token
A.7. RSA Key Used in Examples
Appendix B. Acknowledgements
Appendix C. Notices
§ Authors' Addresses









포토

 
모바일 버전으로 보기