[Openid-specs-mobile-profile] CIBA Issues Review: Feedback for #62

Fri Mar 9 09:30:48 UTC 2018

Hello Gonzalo,

   Here are two remarks about your proposal :

-       I think using the wording ‘spam-code’ to describe an *anti*spam code will introduce some confusion.

-       I’m not sure it’s a good idea to expose the antispam code on CIBA. This code is similar to a user password, so it should be a secret between a user and his MNO. It was created to protect the user in a situation where anybody was able to enter any MSISDN on a public form (e.g. the GSMA discovery page before an OpenId Connect interaction). In CIBA, it’s the SP that will call CIBA, so using an antispam code implies that the secret is also shared amongst all SP (is this still a secret?). On another hand, is there still a spam risk in CIBA? Yes, if SP allow any user to enter any MSISDN, but in this situation the SP should use the classic OpenId Connect flow (because the user is already using the SP to be able to enter a MSISDN). No, if the SP uses CIBA as a second factor. My proposal is that CIBA does not implement antispam code, and that MNO does not check the antispam code when CIBA is used.

   What is your point of view about this proposal?

Best regards,
Nicolas

De : Openid-specs-mobile-profile [mailto:openid-specs-mobile-profile-bounces at lists.openid.net] De la part de GONZALO FERNANDEZ RODRIGUEZ
Envoyé : vendredi 2 mars 2018 14:40
À : openid-specs-mobile-profile at lists.openid.net
Cc : PABLO GUIJARRO ENRIQUEZ
Objet : [Openid-specs-mobile-profile] CIBA Issues Review: Feedback for #62

Hi all,

I continue asking you for feedback about another CIBA issue, in that cases is the #62 https://bitbucket.org/openid/mobile/issues/62/ciba-support-for-spam-prevention-code-in

The spam-code belongs to the end-user, so it should be configured by the end-user in the OpenID Provider.
The CIBA flow doesn't have an interactive session with the end-user, but is the user who is contacted directly in his authentication device, what means that the end-user won't have the possibility to introduce the spam-code in his authentication, so, it only could be done by the Client.

We think that it would be possible to add support for that in CIBA as follow:

1.            A new OPTIONAL field "spam-code" in the CIBA authentication request.
2.            An specific error in case of the end-user had the anti-spam activatedin the OIDC and the Service Provider didn't include it in the authentication request.

It is worth it to highlight that this would be an optional feature implemented by the OIDC's and it should be "out of the scope" of CIBA to define how the end-user would share the spam-code with the Service Provider and how the end-user would configure the spam-code in the OIDC.

I would like to know again your point of view on that in order to resolve this issue.

Best,
Gonza.

________________________________

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

_________________________________________________________________________________________________________________________

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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-mobile-profile/attachments/20180309/bef48d33/attachment-0001.html>