<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi,</p>
<p>@Nat : In your last response, I'm not sure to well understand
what you have in mind. You are talking about a "consent", is this,
as I understand your sentence, related to the "scope" parameter ?
With this hypothesis, when you say "If it can be shown on the
mobile handset to collect the consent", I think that the
collection of consent by the OP for the requested scopes is not
detailed in OpenID Connect specifications, right ? Not sure to
understand what does "content of the transaction" mean and how it
may be manipulated by the OP. <br>
</p>
<p>Do you have in mind an authentication use case (ie a "login into"
functionality) or something different ?</p>
<p>Br,</p>
<p>Charles.</p>
<div class="moz-cite-prefix">Le 02/03/2017 à 19:51, Nat Sakimura a
écrit :<br>
</div>
<blockquote
cite="mid:CABzCy2DF695H0ss51inE-ZNi7cT0MdJsGAJc_3bL+2M8WR8ATQ@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr">So, Financial Institutions has a use case to
display the content of the transaction to be committed in the
mobile handset while the transaction itself is done on a PC. The
handset acts as the more secure second channel. This is to cope
with the Man-in-the-browser attack that rewrites pretty much
everything on the PC screen, i.e., a consent collected on a PC
is moot. Typically, the authorization request is done through a
signed request object. If it can be shown on the mobile handset
to collect the consent, it would be really great.
<div><br>
</div>
<div>Nat</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Fri, Mar 3, 2017 at 1:25 AM GONZALO FERNANDEZ
RODRIGUEZ <<a moz-do-not-send="true"
href="mailto:gonzalo.fernandezrodriguez@telefonica.com">gonzalo.fernandezrodriguez@telefonica.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div
style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif"
class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">Hi guys,</div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">
<div class="gmail_msg">My thoughts on this are that for
an authentication there is no other context than the
client where you are being authenticated, when you
need supply a context with additional information is
because you need the user to authorize something,
unless this is the conclusion I have got in a
nutshell.</div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">As far as I remember the context
parameter is something that was asked to be introduced
in CIBA to address some use cases where the Service
Provider wanted to use an Authentication Flow to do an
action different from "login into". That is what leads
to not introduce the context parameter in CIBA as
these uses cases should be considered Authorization
use cases and thus would be needed to be resolved
using UQ.</div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">Something similar to the current
use cases where the SMS is used to authorize a
transaction in a bank where the bank sends an opaque
string in the SMS was under discussion because in
spite the fact that they are an authorization, is
something that could be perfectly undertaken using the
binding message because you can consider that this
opaque string is somehow to interlock both devices,
however this is something impossible to do in case of
the OP is in charge to generate the binding_message as
I think was the decision of the majority in this WG.</div>
</div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">Best,</div>
<div class="gmail_msg">Gonza.</div>
<div class="gmail_msg">
</div>
</div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<span id="m_6871347971143813910OLK_SRC_BODY_SECTION"
class="gmail_msg">
<div
style="font-family:Calibri;font-size:12pt;text-align:left;color:black;BORDER-BOTTOM:medium
none;BORDER-LEFT:medium
none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df
1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt"
class="gmail_msg">
<span style="font-weight:bold" class="gmail_msg">From: </span>Openid-specs-mobile-profile
<<a moz-do-not-send="true"
href="mailto:openid-specs-mobile-profile-bounces@lists.openid.net"
class="gmail_msg" target="_blank">openid-specs-mobile-profile-bounces@lists.openid.net</a>>
on behalf of "<a moz-do-not-send="true"
href="mailto:Axel.Nennker@telekom.de"
class="gmail_msg" target="_blank">Axel.Nennker@telekom.de</a>"
<<a moz-do-not-send="true"
href="mailto:Axel.Nennker@telekom.de"
class="gmail_msg" target="_blank">Axel.Nennker@telekom.de</a>><br
class="gmail_msg">
<span style="font-weight:bold" class="gmail_msg">Date: </span>jueves,
2 de marzo de 2017, 12:54<br class="gmail_msg">
<span style="font-weight:bold" class="gmail_msg">To: </span>"<a
moz-do-not-send="true"
href="mailto:charles.marais@orange.com"
class="gmail_msg" target="_blank">charles.marais@orange.com</a>"
<<a moz-do-not-send="true"
href="mailto:charles.marais@orange.com"
class="gmail_msg" target="_blank">charles.marais@orange.com</a>>,
John Bradley <<a moz-do-not-send="true"
href="mailto:ve7jtb@ve7jtb.com" class="gmail_msg"
target="_blank">ve7jtb@ve7jtb.com</a>>, "<a
moz-do-not-send="true"
href="mailto:Joerg.Connotte@telekom.de"
class="gmail_msg" target="_blank">Joerg.Connotte@telekom.de</a>"
<<a moz-do-not-send="true"
href="mailto:Joerg.Connotte@telekom.de"
class="gmail_msg" target="_blank">Joerg.Connotte@telekom.de</a>>,
"<a moz-do-not-send="true"
href="mailto:openid-specs-mobile-profile@lists.openid.net"
class="gmail_msg" target="_blank">openid-specs-mobile-profile@lists.openid.net</a>"
<<a moz-do-not-send="true"
href="mailto:openid-specs-mobile-profile@lists.openid.net"
class="gmail_msg" target="_blank">openid-specs-mobile-profile@lists.openid.net</a>></div>
</span></div>
<div
style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif"
class="gmail_msg"><span
id="m_6871347971143813910OLK_SRC_BODY_SECTION"
class="gmail_msg">
<div
style="font-family:Calibri;font-size:12pt;text-align:left;color:black;BORDER-BOTTOM:medium
none;BORDER-LEFT:medium
none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df
1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt"
class="gmail_msg"><br class="gmail_msg">
<span style="font-weight:bold" class="gmail_msg">Subject:
</span>Re: [Openid-specs-mobile-profile] CIBA context
client_name<br class="gmail_msg">
</div>
</span></div>
<div
style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif"
class="gmail_msg"><span
id="m_6871347971143813910OLK_SRC_BODY_SECTION"
class="gmail_msg">
<div class="gmail_msg"><br class="gmail_msg">
</div>
<span class="gmail_msg">
<div class="gmail_msg">
<div bgcolor="white" link="blue" vlink="purple"
class="gmail_msg" lang="EN-US">
<div class="m_6871347971143813910WordSection1
gmail_msg">
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg">Hi Charles,</span></p>
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg"> </span></p>
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg">The GSMA’s document “OpenID
Connect Mobile Connect Profile 2.1” specifies
“context” parameter.</span></p>
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg">When I remember correctly we
decided in MODRNA to not have that in CIBA.</span></p>
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg">Now a DT Natco asked for
this feature in backchannel requests.</span></p>
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg"> </span></p>
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg">I did not have a use case at
hand. I guess the prerequisites are: use back
channel to get access token with SP provided
text and a variable client_name.</span></p>
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg">Probably some Mobile Connect
use cases could be envisioned to have an SP
provided text during authentication and
consent collection.</span></p>
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg"> </span></p>
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg">The WG felt that in CIBA the
OP is ultimately responsible for those “pages”
and we should not step into this unchartered
land now.</span></p>
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg">But I wanted to raise this
again to see whether this is still the
opinion.</span></p>
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg"> </span></p>
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg">Cheers</span></p>
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg">Axel</span></p>
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg"> </span></p>
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg"> </span></p>
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg"> </span></p>
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg"> </span></p>
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg"> </span></p>
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg"> </span></p>
<div class="gmail_msg" align="center">
<table class="m_6871347971143813910MsoTableGrid
gmail_msg"
style="border-collapse:collapse;border:none"
border="1" cellpadding="0" cellspacing="0"
width="652">
<tbody class="gmail_msg">
<tr style="page-break-inside:avoid"
class="gmail_msg">
<td style="width:91.9pt;border:solid
windowtext 1.0pt;padding:0cm 5.4pt 0cm
5.4pt" class="gmail_msg" valign="top"
width="123">
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">acr_values</span></p>
</td>
<td style="width:3.0cm;border:solid
windowtext
1.0pt;border-left:none;padding:0cm 5.4pt
0cm 5.4pt" class="gmail_msg"
valign="top" width="113">
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">Mandatory</span></p>
</td>
<td style="width:3.0cm;border:solid
windowtext
1.0pt;border-left:none;padding:0cm 5.4pt
0cm 5.4pt" class="gmail_msg"
valign="top" width="113">
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">Mandatory</span></p>
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB"> </span></p>
</td>
<td style="width:8.0cm;border:solid
windowtext
1.0pt;border-left:none;padding:0cm 5.4pt
0cm 5.4pt" class="gmail_msg"
valign="top" width="302">
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">Authentication Context
Class Reference. Space separated
string that specifies the
Authentication Context Reference
used during authentication
processing. The RP/Client can use
LoA for a particular use case. The
values appear in order of
preference. The acr satisfied by the
authentication is returned as the
acr claim value. ID GW MUST consider
only the first value in the list,
and ignores remaining LoA values
while processing the request.
</span></p>
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">The recommended values
are the LoAs as specified in ISO/IEC
29115 Clause 6 – 1, 2, 3, 4 –
representing the LoAs of LOW,
MEDIUM, HIGH and VERY HIGH.
</span></p>
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">The acr_values are an
indication of what authentication
method to use by the ID GW. The
usage of authentication methods
depends on the LoA value passed in
the parameter acr_values. The ID GW
configures the authentication method
selection logic based on the
acr_values.</span></p>
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">ID GW/Authorization
server MUST return the achieved
level of assurance in the acr
parameter.</span></p>
</td>
</tr>
<tr style="page-break-inside:avoid"
class="gmail_msg">
<td style="width:91.9pt;border:solid
windowtext
1.0pt;border-top:none;padding:0cm 5.4pt
0cm 5.4pt" class="gmail_msg"
valign="top" width="123">
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">binding_message</span></p>
</td>
<td
style="width:3.0cm;border-top:none;border-left:none;border-bottom:solid
windowtext 1.0pt;border-right:solid
windowtext 1.0pt;padding:0cm 5.4pt 0cm
5.4pt" class="gmail_msg" valign="top"
width="113">
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">Optional</span></p>
</td>
<td
style="width:3.0cm;border-top:none;border-left:none;border-bottom:solid
windowtext 1.0pt;border-right:solid
windowtext 1.0pt;padding:0cm 5.4pt 0cm
5.4pt" class="gmail_msg" valign="top"
width="113">
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">Optional </span></p>
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">[Mandatory if scope =
“openid mc_authz”]</span></p>
</td>
<td
style="width:8.0cm;border-top:none;border-left:none;border-bottom:solid
windowtext 1.0pt;border-right:solid
windowtext 1.0pt;padding:0cm 5.4pt 0cm
5.4pt" class="gmail_msg" valign="top"
width="302">
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">Client provided plain
text, "reference or ID" to interlock
consumption device and authorization
device for a better user experience.
The message will be displayed on
consumption device and mobile
device. Empty values are allowed.
(zero length)</span></p>
</td>
</tr>
<tr style="page-break-inside:avoid"
class="gmail_msg">
<td style="width:91.9pt;border:solid
windowtext
1.0pt;border-top:none;padding:0cm 5.4pt
0cm 5.4pt" class="gmail_msg"
valign="top" width="123">
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">client_name</span></p>
</td>
<td
style="width:3.0cm;border-top:none;border-left:none;border-bottom:solid
windowtext 1.0pt;border-right:solid
windowtext 1.0pt;padding:0cm 5.4pt 0cm
5.4pt" class="gmail_msg" valign="top"
width="113">
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">Optional</span></p>
</td>
<td
style="width:3.0cm;border-top:none;border-left:none;border-bottom:solid
windowtext 1.0pt;border-right:solid
windowtext 1.0pt;padding:0cm 5.4pt 0cm
5.4pt" class="gmail_msg" valign="top"
width="113">
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">Optional [Mandatory if
scope = “openid mc_authz”]</span></p>
</td>
<td
style="width:8.0cm;border-top:none;border-left:none;border-bottom:solid
windowtext 1.0pt;border-right:solid
windowtext 1.0pt;padding:0cm 5.4pt 0cm
5.4pt" class="gmail_msg" valign="top"
width="302">
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">A short name to
identify RP/Client application and
must be displayed on authentication/
authorisation device.
</span></p>
</td>
</tr>
<tr style="page-break-inside:avoid"
class="gmail_msg">
<td style="width:91.9pt;border:solid
windowtext
1.0pt;border-top:none;padding:0cm 5.4pt
0cm 5.4pt" class="gmail_msg"
valign="top" width="123">
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">context</span></p>
</td>
<td
style="width:3.0cm;border-top:none;border-left:none;border-bottom:solid
windowtext 1.0pt;border-right:solid
windowtext 1.0pt;padding:0cm 5.4pt 0cm
5.4pt" class="gmail_msg" valign="top"
width="113">
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">Optional </span></p>
</td>
<td
style="width:3.0cm;border-top:none;border-left:none;border-bottom:solid
windowtext 1.0pt;border-right:solid
windowtext 1.0pt;padding:0cm 5.4pt 0cm
5.4pt" class="gmail_msg" valign="top"
width="113">
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">Optional </span></p>
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">[Mandatory if scope =
“openid mc_authz”]</span></p>
</td>
<td
style="width:8.0cm;border-top:none;border-left:none;border-bottom:solid
windowtext 1.0pt;border-right:solid
windowtext 1.0pt;padding:0cm 5.4pt 0cm
5.4pt" class="gmail_msg" valign="top"
width="302">
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">A Transaction/action
based message displayed on
authorization device and must
provide by RP/client. If scope =
"openid mc_authz”.
</span></p>
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB"> </span></p>
</td>
</tr>
<tr style="page-break-inside:avoid"
class="gmail_msg">
<td style="width:91.9pt;border:solid
windowtext
1.0pt;border-top:none;padding:0cm 5.4pt
0cm 5.4pt" class="gmail_msg"
valign="top" width="123">
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">response_mode</span></p>
</td>
<td
style="width:3.0cm;border-top:none;border-left:none;border-bottom:solid
windowtext 1.0pt;border-right:solid
windowtext 1.0pt;padding:0cm 5.4pt 0cm
5.4pt" class="gmail_msg" valign="top"
width="113">
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">Optional </span></p>
</td>
<td
style="width:3.0cm;border-top:none;border-left:none;border-bottom:solid
windowtext 1.0pt;border-right:solid
windowtext 1.0pt;padding:0cm 5.4pt 0cm
5.4pt" class="gmail_msg" valign="top"
width="113">
<p class="m_6871347971143813910TableText
gmail_msg"><span class="gmail_msg"
lang="EN-GB">Optional </span></p>
</td>
<td
style="width:8.0cm;border-top:none;border-left:none;border-bottom:solid
windowtext 1.0pt;border-right:solid
windowtext 1.0pt;padding:0cm 5.4pt 0cm
5.4pt" class="gmail_msg" valign="top"
width="302">
<p class="m_6871347971143813910TableText
gmail_msg"><span
style="color:black;background:white"
class="gmail_msg" lang="EN-GB">Informs
the Authorization Server of the
mechanism to be used for returning
parameters from the Authorization
Endpoint</span></p>
<p class="m_6871347971143813910TableText
gmail_msg"><span
style="color:black;background:white"
class="gmail_msg" lang="EN-GB">Can
be used when there is no user agent
/browser.</span><span
class="gmail_msg" lang="EN-GB"></span></p>
</td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg"> </span></p>
<p class="MsoNormal gmail_msg"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"
class="gmail_msg"> </span></p>
<div class="gmail_msg">
<div style="border:none;border-top:solid #b5c4df
1.0pt;padding:3.0pt 0cm 0cm 0cm"
class="gmail_msg">
<p class="MsoNormal gmail_msg"><b
class="gmail_msg"><span
style="font-size:10pt;font-family:Tahoma,sans-serif;color:windowtext"
class="gmail_msg">From:</span></b><span
style="font-size:10pt;font-family:Tahoma,sans-serif;color:windowtext"
class="gmail_msg">
<a moz-do-not-send="true"
href="mailto:charles.marais@orange.com"
class="gmail_msg" target="_blank">charles.marais@orange.com</a>
[<a moz-do-not-send="true"
href="mailto:charles.marais@orange.com"
class="gmail_msg" target="_blank">mailto:charles.marais@orange.com</a>]
<br class="gmail_msg">
<b class="gmail_msg">Sent:</b> Wednesday,
March 01, 2017 3:19 PM<br
class="gmail_msg">
<b class="gmail_msg">To:</b> Nennker,
Axel; <a moz-do-not-send="true"
href="mailto:ve7jtb@ve7jtb.com"
class="gmail_msg" target="_blank">ve7jtb@ve7jtb.com</a>;
Connotte, Jörg;
<a moz-do-not-send="true"
href="mailto:openid-specs-mobile-profile@lists.openid.net"
class="gmail_msg" target="_blank">openid-specs-mobile-profile@lists.openid.net</a><br
class="gmail_msg">
<b class="gmail_msg">Cc:</b> AILLERY
Nicolas IMT-OLPS; CLEMENT Philippe IMT
TECHNO<br class="gmail_msg">
<b class="gmail_msg">Subject:</b> Re:
[Openid-specs-mobile-profile] CIBA context
client_name</span></p>
</div>
</div>
<p class="MsoNormal gmail_msg"> </p>
<p class="gmail_msg">Hi Axel,<br class="gmail_msg">
<br class="gmail_msg">
Could you share the detailed uses cases in which
the "context" parameter would be used ? Are they
mentioned in the attached file (GSMA's uses
cases list) ? Do these uses cases have some
adherence with the GSMA authorization product ?<br
class="gmail_msg">
<br class="gmail_msg">
Could we have some examples of what the
"context" would contain ? Is it clearly
different from a question or a validation ?<br
class="gmail_msg">
<br class="gmail_msg">
As a reminder, User Questioning should be the
OIDF specification to address the GSMA
Authorization product.<br class="gmail_msg">
<br class="gmail_msg">
I think that the relevance of the "context"
parameter should only be discussed, both in CPAS
and in Modrna, depending of the uses cases for
which it would be relevant.</p>
<p class="gmail_msg">Br,</p>
<p class="gmail_msg">Charles.</p>
<p class="MsoNormal gmail_msg"> </p>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg">Le 28/02/2017 à
22:31, <a moz-do-not-send="true"
href="mailto:Axel.Nennker@telekom.de"
class="gmail_msg" target="_blank">
Axel.Nennker@telekom.de</a> a écrit :</p>
</div>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt"
class="gmail_msg">
<pre class="gmail_msg"><span style="color:#1f497d" class="gmail_msg" lang="DE">Hi,</span></pre>
<pre class="gmail_msg"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)" class="gmail_msg" lang="DE"> </span></pre>
<pre class="gmail_msg"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)" class="gmail_msg">some telcos would like to offer to service providers the option to display text during authentication and consent collection.</span></pre>
<pre class="gmail_msg"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)" class="gmail_msg">The OP does still control what is displayed.</span></pre>
<pre class="gmail_msg"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)" class="gmail_msg">Should we add what CPAS calls context and client_name or should that be an extension by CPAS?</span></pre>
<pre class="gmail_msg"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)" class="gmail_msg"> </span></pre>
<pre class="gmail_msg"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)" class="gmail_msg">Cheers</span></pre>
<pre class="gmail_msg"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)" class="gmail_msg">Axel</span></pre>
<p class="MsoNormal gmail_msg"><br
class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
</p>
<pre class="gmail_msg">_______________________________________________</pre>
<pre class="gmail_msg">Openid-specs-mobile-profile mailing list</pre>
<pre class="gmail_msg"><a moz-do-not-send="true" href="mailto:Openid-specs-mobile-profile@lists.openid.net" class="gmail_msg" target="_blank">Openid-specs-mobile-profile@lists.openid.net</a></pre>
<pre class="gmail_msg"><a moz-do-not-send="true" href="http://lists.openid.net/mailman/listinfo/openid-specs-mobile-profile" class="gmail_msg" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-mobile-profile</a></pre>
</blockquote>
<p class="MsoNormal gmail_msg"> </p>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"
style="margin-bottom:12.0pt">-- <br
class="gmail_msg">
<span
style="font-size:10pt;font-family:Times,serif"
class="gmail_msg"><img
moz-do-not-send="true"
id="m_6871347971143813910_x0000_i1025"
src="cid:image001.gif@01D2934C.C92553F0"
class="gmail_msg" border="0" height="40"
width="40"><br class="gmail_msg">
<br class="gmail_msg">
<b class="gmail_msg">MARAIS Charles </b><br
class="gmail_msg">
<b class="gmail_msg">Orange Labs Lannion</b><br
class="gmail_msg">
Tel : <a moz-do-not-send="true"
href="tel:+33%202%2096%2007%2024%2018"
value="+33296072418" class="gmail_msg"
target="_blank">+33 (0)2 96 07 24 18</a> <br
class="gmail_msg">
<a moz-do-not-send="true"
href="mailto:charles.marais@orange.com"
class="gmail_msg" target="_blank">charles.marais@orange.com</a><br
class="gmail_msg">
Orange Labs Lannion <br class="gmail_msg">
2, avenue Pierre Marzin <br
class="gmail_msg">
22307 LANNION Cedex - France <br
class="gmail_msg">
<br class="gmail_msg">
</span></p>
</div>
<pre class="gmail_msg">_________________________________________________________________________________________________________________________</pre>
<pre class="gmail_msg"> </pre>
<pre class="gmail_msg">Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc</pre>
<pre class="gmail_msg">pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler</pre>
<pre class="gmail_msg">a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,</pre>
<pre class="gmail_msg">Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.</pre>
<pre class="gmail_msg"> </pre>
<pre class="gmail_msg">This message and its attachments may contain confidential or privileged information that may be protected by law;</pre>
<pre class="gmail_msg">they should not be distributed, used or copied without authorisation.</pre>
<pre class="gmail_msg">If you have received this email in error, please notify the sender and delete this message and its attachments.</pre>
<pre class="gmail_msg">As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.</pre>
<pre class="gmail_msg">Thank you.</pre>
</div>
</div>
</div>
</span></span></div>
_______________________________________________<br
class="gmail_msg">
Openid-specs-mobile-profile mailing list<br class="gmail_msg">
<a moz-do-not-send="true"
href="mailto:Openid-specs-mobile-profile@lists.openid.net"
class="gmail_msg" target="_blank">Openid-specs-mobile-profile@lists.openid.net</a><br
class="gmail_msg">
<a moz-do-not-send="true"
href="http://lists.openid.net/mailman/listinfo/openid-specs-mobile-profile"
rel="noreferrer" class="gmail_msg" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-mobile-profile</a><br
class="gmail_msg">
</blockquote>
</div>
<div dir="ltr">-- <br>
</div>
<div data-smartmail="gmail_signature">
<p dir="ltr">Nat Sakimura</p>
<p dir="ltr">Chairman of the Board, OpenID Foundation</p>
</div>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<font face="TIMES"><font size="2">
<img src="cid:part24.59A4C0E5.E7BEF3B4@orange.com" <br="">
<font color="BLACK">
<br>
<b> MARAIS Charles </b><br>
<b> Orange Labs Lannion</b></font><br>
Tel : +33 (0)2 96 07 24 18 <br>
<a href="mailto:charles.marais@orange.com">charles.marais@orange.com</a><br>
Orange Labs Lannion <br>
2, avenue Pierre Marzin <br>
22307 LANNION Cedex - France
<br>
<br>
<br>
</font></font></div>
<PRE>_________________________________________________________________________________________________________________________
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.
</PRE></body>
</html>