1、 ETSI TR 1Universal Mobile TelStudy on SecuSingle Sigwith 3GPP operator-co(3GPP TR 33.9TECHNICAL REPORT 133 995 V13.0.0 (2016elecommunications System (LTE; rity aspects of integration oign-On (SSO) frameworks controlled resources and mec.995 version 13.0.0 Release 1316-03) (UMTS); n of echanisms 13)
2、 ETSI ETSI TR 133 995 V13.0.0 (2016-03)13GPP TR 33.995 version 13.0.0 Release 13Reference RTR/TSGS-0333995vd00 Keywords LTE, UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but n
3、on lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions o
4、f the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific
5、network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in t
6、he present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as a
7、uthorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM,
8、 PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Asso
9、ciation. ETSI ETSI TR 133 995 V13.0.0 (2016-03)23GPP TR 33.995 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for E
10、TSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/
11、ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essentia
12、l to the present document. Foreword This Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as bei
13、ng references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “
14、will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TR 133 995 V13.0.0 (2016-03)33GPP TR 33
15、.995 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations 6g34 Relation of the present study to other related work in 3GPP . 6g35 P
16、otential requirements identified in the present study . 7g36 Solutions for Liberty Alliance/SAML 3GPP interworking . 7g36.1 General . 7g37 Solutions for OpenID 3GPP interworking 7g37.1 General . 7g37.2 GBA Lite 7g37.2.1 Rationale for solution 7g37.2.2 Solution description 8g37.2.2.1 Architecture . 8
17、g37.2.2.2 BSF Implementation optimizations . 8g37.2.2.3 Message Flow . 9g37.2.3 Evaluation against SA1 requirements . 10g37.3 Third Party IdP binding for two-factor authentication . 10g37.3.1 Rationale for solution 10g37.3.3 Solution 1 description . 12g37.3.3.1 General 12g37.3.3.2 Example solutions
18、for two factor authentication . 14g37.3.4 Solution 2 description . 18g37.3.4.1 Solution based on OpenID-GBA interworking where OTT performs username/password authentication 18g37.3.4.2 Solution based on OpenID-GBA interworking where MNO performs both GBA and username/password authentication 19g37.3.
19、5 Evaluation against SA1 requirements . 21g37.4 Using user consent for GBA and SSO 23g37.4.1 Rationale for solution 23g37.4.2 Solution description 23g37.4.2.1 General 23g37.4.2.2 GBA_ME-based solution 24g37.4.2.3 GBA_U-based solution . 26g37.4.3 Functional Architecture 28g37.4.4 Evaluation against S
20、A1 requirements . 29g37.5 3rd party SSO identity mapping . 32g37.5.1 Rationale for solution 32g37.5.2 Solution description 32g37.5.3 Evaluation against SA1 requirements . 34g38 Conclusions 36g3Annex A: Change history 37g3History 38 ETSI ETSI TR 133 995 V13.0.0 (2016-03)43GPP TR 33.995 version 13.0.0
21、 Release 13Foreword This Technical Report has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it
22、 will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y t
23、he second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TR 133 995 V13.0.0 (2016-03)53GPP TR 33.995 version 13.0.0 Release 131 S
24、cope The present study investigates the security aspects of the service requirements specified by SA1 in TS 22.101 11 clause 26, on the integration of SSO frameworks with 3GPP networks for various operator authentication configurations (e.g. configurations using GBA or not using GBA). In particular,
25、 this study evaluates existing interworking solutions between SSO frameworks and 3GPP authentication mechanisms against the SA1 service requirements. The study is not limited to evaluation of existing interworking solutions and new interworking solutions may be developed as appropriate. The study co
26、vers the security requirements to enable the operator to become the preferred SSO Identity Provider by allowing the usage of credentials on the UE for SSO services, as well as ways for the 3GPP operator to leverage its trust framework and its reliable and robust secure credential handling infra-stru
27、cture to provide SSO service based on operator-controlled credentials. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, ve
28、rsion number, etc.) or non-specific. - For a specific reference, subsequent revisions do not apply. - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version o
29、f that document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TR 22.895: “Study on Service aspects of integration of Single Sign-On (SSO) frameworks with 3GPP operator-controlled resources and mechanisms“. 3 3GPP TR 33.980: “Interworking
30、of Liberty Alliance Identity Federation Framework (ID-FF), Identity Web Service Framework (ID-WSF) and the Generic Authentication Architecture (GAA)“. 4 3GPP TR 33.924: “Identity management and 3GPP security interworking; Identity management and Generic Authentication Architecture (GAA) interworking
31、“. 5 3GPP TR 33.804: “Single Sign On Application Security for Common IMS based on SIP Digest“. 6 3GPP TS 33.220: “Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture“. 7 3GPP TS 24.109: “Bootstrapping interface (Ub) and network application function interface (Ua); Protocol
32、details“. 8 3GPP TS 29.109: “Generic Authentication Architecture (GAA); Zh and Zn Interfaces based on the Diameter protocol; Stage 3“. 9 OpenID Foundation “OpenID Authentication 2.0“, http:/ 10 3GPP TS 33.222, Access to network application functions using Hypertext Transfer Protocol over Transport L
33、ayer Security (HTTPS) 11 3GPP TS 22.101, Service aspects; Service principles. 12 3GPP TR 33.905, “Recommendations for trusted open platforms“. ETSI ETSI TR 133 995 V13.0.0 (2016-03)63GPP TR 33.995 version 13.0.0 Release 1313 OpenID Foundation “OpenID Provider Authentication Policy Extension 1.0“, ht
34、tp:/ 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1, TS 22.101 11 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 1. e
35、xample: text used to clarify abstract rules by applying them literally. Authorization: a mechanism or process which determines what a particular user or a group of users can access or do. Multi-factor authentication: a method of logon verification where at least two different factors of proof are pr
36、ovided, and jointly verified. There are three generally recognized types of authentication factors: Type 1 - Something You Know. Type 1 includes, but is not limited to, passwords, PINs, combinations, code words, or secret handshakes. Anything that a user can remember and then type, say, do, perform,
37、 or otherwise recall when needed falls into this category. Type 2 - Something You Have. Type 2 includes all items that are physical objects, such as, but not limited to, keys, smart phones, smart cards, USB drives, and token devices. (A token device produces a time-based PIN or can compute a respons
38、e from a challenge number issued by the server.) Type 3 - Something You Are. Type 3 includes any part of the human body that can be offered for verification, such as, but not limited to, fingerprints, palm scanning, facial recognition, retina scans, iris scans, and voice verification. Multi-step aut
39、hentication: a method of logon verification where the authentication can take several steps or phases to complete. Multi-step authentication differs from multi-factor authentication in that it does not strictly require that each authentication factor be different, or that multiple factors are evalua
40、ted in conjunction. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 1, TS 22.101 11 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 1. IdP Ide
41、ntity Provider RP Relaying Party SSO Single Sign-On 4 Relation of the present study to other related work in 3GPP Other SSO related work in 3GPP Completed SA1 work - SSO requirements, TS 22.101 11 clause 26; - Study on integration of SSO frameworks with 3GPP, TR 22.8952. Completed SA3 work ETSI ETSI
42、 TR 133 995 V13.0.0 (2016-03)73GPP TR 33.995 version 13.0.0 Release 13- Liberty - GBA interworking, TR 33.980 3; - OpenID GBA interworking, TR 33.924 4. - SSO with SIP Digest, TR 33.804 5. What is the relation of this study to other work in 3GPP This study evaluates the completed and ongoing SA3 SSO
43、 work against the service requirements identified bySA1 in TS 22.101 11 clause 26. All input in this study is intended to have a clear relation to the SA1 service requirements. This study is not intended duplicate functionality supporting SA1 service requirements, when such functionality can be offe
44、red by existing SSO mechanisms. In particular existing solutions in other SA3 specifications are evaluated and new ones can be proposed only if the existing solutions would not meet the SA1 service requirements. 5 Potential requirements identified in the present study The purpose of this clause is t
45、o identify potential security requirements in the present study, if any. The requirements may be general or specific to identified SSO frameworks as seen appropriate. NOTE: No potential requirements were identified in the present study. 6 Solutions for Liberty Alliance/SAML 3GPP interworking 6.1 Gen
46、eral The purpose of this clause is to investigate the existing (and possible new) solutions for interworking of Liberty Alliance/SAML and 3GPP authentication mechanisms and evaluate the solutions against the SA1 requirements. NOTE: No solutions were investigated under this clause. 7 Solutions for Op
47、enID 3GPP interworking 7.1 General The purpose of this clause is to investigate the existing (and possible new) solutions for interworking of OpenID and 3GPP authentication mechanisms and evaluate the solutions against the SA1 requirements. 7.2 GBA Lite 7.2.1 Rationale for solution SSO has been iden
48、tified as one of the most promising applications of GBA. Clearly, the value of this use-case for an external service provider depends on the number of supporting users. This number in turn depends on the availability of GBA-capable phones and the number of operators which have deployed the necessary
49、 GBA infrastructure ETSI ETSI TR 133 995 V13.0.0 (2016-03)83GPP TR 33.995 version 13.0.0 Release 13One way to overcome the initial threshold of supporting users is to simplify the deployment process. This is accomplished using an SSO specific implementation option of GBA called GBA Lite. Later on, if an operator finds a need to support other applications as well, the SSO specific version can be extended to full GBA. The solution presented here closely follows the GBA and OpenID in
