[Openid-specs-mobile-profile] Issue #1: Context
j.connotte at telekom.de
Wed Jul 1 07:52:08 UTC 2015
in our last call we had a lengthy discussion about Issue #1.
In my opinion we are talking about two different use cases where context is useful. But the requirements about the context are very different for those use cases
1) Context for authentication/login. Here the purpose of the context is to create an interlock between the consumption device and the authentication device to allow the user to make sure that the request to log in really comes from a process he himself initiated on the consumption device. To facilitate this some nonsense text would be sufficient. In any case there is no need to have a structured context or some mechanisms to process the context besides show the context-text on the authentication device AND the consumption device.
2) Context to authorize business transactions (e.g. payment transactions). Here the purpose of the context is to make sure that the user is aware that he has to authorize a certain transaction which does not necessary include a primary authentication. This implies that the context is highly structured and is processed in the IdP. For example for a payment transaction the IdP has to understand that this is a payment transaction and has to store context (and possibly the whole transaction) to allow for non-repudiation issues.
What do you think?
Deutsche Telekom AG
Products & Innovation
T-Online-Allee 1, 64295 Darmstadt
+49 6151 680-7288 (Tel.)
+49 151 184-15517 (Mobil)
E-Mail: j.connotte at telekom.de<mailto:j.connotte at telekom.de>
Life is for sharing.
You can find the obligatory information on www.telekom.com/compulsory-statement<http://www.telekom.com/compulsory-statement>
Big changes start small - conserve resources by not printing every e-mail.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openid-specs-mobile-profile