[Openid-specs-mobile-profile] Issue #1: Context

GONZALO FERNANDEZ RODRIGUEZ gonzalo.fernandezrodriguez at telefonica.com
Sun Jul 5 12:45:17 UTC 2015

My 2 cents...,

I also agree that there are these two different use cases. In my humble opinion both are authentication use cases from the point of view of Mobile Connect, and is the service provider who use this authentication to authorize a transaction.

I am not sure if the IDP should process the context, store the values of the transaction, etc. I am not saying that is possible, but I guess that is something complicate to generalize to all kind of transactions. It seems to me a solution too much ambitious that will require a lot of effort in bot sides (OP and RP), specially in the OP. Could there be a simpler alternative solution (at least in a first phase) to only allow provide this context in order to the user could compare with the transaction in the RP (e.g: the bank) ? I am talking about a simpler solution like the solution that they have nowdays transaction_id + amount in an SMS?


De: "philippe.clement at orange.com<mailto:philippe.clement at orange.com>" <philippe.clement at orange.com<mailto:philippe.clement at orange.com>>
Fecha: jueves 2 de julio de 2015 17:09
Para: "Connotte, Joerg" <j.connotte at telekom.de<mailto:j.connotte at telekom.de>>, "openid-specs-mobile-profile at lists.openid.net<mailto:openid-specs-mobile-profile at lists.openid.net>" <openid-specs-mobile-profile at lists.openid.net<mailto:openid-specs-mobile-profile at lists.openid.net>>
Asunto: Re: [Openid-specs-mobile-profile] Issue #1: Context

Hi Joerg,

I agree on the differences between the 2 use cases, and the description you made.

On Use Case 2, I'm wondering on the meaning of "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".
Does it mean that no authentication at all may have occurred before the transaction confirmation request, or at least some other types of authentication ?

On another hand, do you consider that the use case 2 enters into the "consent" perimeter ?


De : Openid-specs-mobile-profile [mailto:openid-specs-mobile-profile-bounces at lists.openid.net] De la part de Connotte, Joerg
Envoyé : mercredi 1 juillet 2015 09:52
À : openid-specs-mobile-profile at lists.openid.net<mailto:openid-specs-mobile-profile at lists.openid.net>
Objet : [Openid-specs-mobile-profile] Issue #1: Context

Hi all,

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?

Kind Regards
Jörg Connotte

Deutsche Telekom AG
Products & Innovation
Jörg Connotte
Customer Platforms
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.


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-mobile-profile/attachments/20150705/7079f41e/attachment-0001.html>

More information about the Openid-specs-mobile-profile mailing list