Content deleted Content added
m →Technical overview: BSF = Bootstrapping Server Function |
Rescuing 2 sources and tagging 0 as dead.) #IABot (v2.0.9.5 |
||
| (16 intermediate revisions by 14 users not shown) | |||
Line 1:
'''Generic Bootstrapping Architecture''' ('''GBA''') is a technology that enables the authentication of a user. This authentication is possible if the user owns a valid identity on
GBA is standardized at the [[3GPP]] (http://www.3gpp.org/ftp/Specs/html-info/33220.htm)
GBA authenticates by making a network component challenge the
Instead of asking the service provider to trust the [[Bootstrapping Server Function|BSF]] and relying on it for every authentication request, the [[Bootstrapping Server Function|BSF]] establishes a shared secret between the [[simcard]] card and the service provider. This shared secret is limited in time and for a specific ___domain.
[[Image:
==Strong points==
This solution has some strong points of certificate and shared secrets without having some of their weaknesses:
- There is no need for user enrollment phase nor secure deployment of keys, making this solution a very low cost one when compared to [[Public key infrastructure|PKI]].
- Another advantage is the ease with which the authentication method may be integrated into terminals and service providers, as it is based on [[HTTP]]'s well known "[[Digest access authentication]]". Every Web server already implement HTTP [[digest authentication]] and the effort to implement GBA on top of digest authentication is minimal. For example, it could be implemented on SimpleSAMLPhP http://rnd.feide.no/simplesamlphp {{Webarchive|url=https://web.archive.org/web/20081219004332/http://rnd.feide.no/simplesamlphp |date=2008-12-19 }} with 500 PHP lines of code and only a few tens of lines of code are Service Provider specific making it really easy to port it to another Web site.
- On device side is needed:
Line 21:
== Technical overview ==
Actually, contents in this section are from external literature.<ref>
There are two ways to use GAA (Generic Authentication Architecture).
Line 33:
Figure above shows the network GAA entities and interfaces between them. Optional entities are drawn with lines
network and borders dotted the scoreboard. The User Equipment (UE) is, for example, the user's mobile phone. The UE and
'''Bootstrapping Server Function''' ('''BSF''') mutually authenticate themselves during the Ub (number [2] above) interface, using the [[Digest access authentication]] [[AKA (security)|AKA]] protocol. The UE also communicates with the '''Network Application Functions''' ('''NAF'''), which are the implementation servers, over the Ua [4] interface, which can use any specific application protocol necessary.
BSF retrieves data from the subscriber from the Home Subscriber Server (HSS) during the Zh [3] interface, which uses the
Line 41:
== Uses ==
* The SPICE project developed an extended Use Case named "split terminal" where a user on a PC can authenticate with
* The research institute [[Fraunhofer
* The Open Mobile Terminal Platform http://www.omtp.org references GBA in its Advanced Trusted Environment: OMTP TR1<ref>
Sadly, despite many advantages and potential uses of GBA, its implementation in handsets has been limited since GBA standardization in 2006. Most notably, GBA was implemented in Symbian-based handsets.
== References ==
| |||