<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Apple Color Emoji";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:196627736;
mso-list-type:hybrid;
mso-list-template-ids:-1560910128 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoPlainText">No, but yes, as I think that is a use case within this broader use case. This is about an two entities having differing 'client' relationships as it relates to the spec. High level:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoPlainText" style="mso-list:l0 level1 lfo1">An typical OIDC “client” starts a registration process.<o:p></o:p></li><li class="MsoPlainText" style="mso-list:l0 level1 lfo1">But the registration serves 2 purposes:<o:p></o:p></li><ol style="margin-top:0in" start="1" type="a">
<li class="MsoPlainText" style="mso-list:l0 level2 lfo1">Register the "client” as an OAUTH consumer of a RESTful API (e.g. the authZ server)<o:p></o:p></li><li class="MsoPlainText" style="mso-list:l0 level2 lfo1">At the exact same time, register the “client” as an OIDC provider with the entity that is the authServer in step a. The hunter becomes the hunted. Or the server becomes the client.<o:p></o:p></li><li class="MsoPlainText" style="mso-list:l0 level2 lfo1">End result: the client in Step a can gain access to API’s as an OAuth client. The client in Step a can federate identities to web applications hosted by the API provider.<o:p></o:p></li></ol>
</ol>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">On 3/20/19, 10:07 AM, "Openid-specs-igov on behalf of Kelts, David via Openid-specs-igov" <openid-specs-igov-bounces@lists.openid.net on behalf of openid-specs-igov@lists.openid.net> wrote:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> Does #2 mean support for (multiple) Attribute Providers in that the OP could gather attributes from an API on behalf of the Digital Subject?<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> David<o:p></o:p></p>
<p class="MsoPlainText"> <span style="font-family:"Apple Color Emoji"">🌿</span>Sent from my iPhone<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> > On Mar 20, 2019, at 8:00 AM, "openid-specs-igov-request@lists.openid.net" <openid-specs-igov-request@lists.openid.net> wrote:<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > Send Openid-specs-igov mailing list submissions to<o:p></o:p></p>
<p class="MsoPlainText"> > openid-specs-igov@lists.openid.net<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > To subscribe or unsubscribe via the World Wide Web, visit<o:p></o:p></p>
<p class="MsoPlainText"> > http://lists.openid.net/mailman/listinfo/openid-specs-igov<o:p></o:p></p>
<p class="MsoPlainText"> > or, via email, send a message with subject or body 'help' to<o:p></o:p></p>
<p class="MsoPlainText"> > openid-specs-igov-request@lists.openid.net<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > You can reach the person managing the list at<o:p></o:p></p>
<p class="MsoPlainText"> > openid-specs-igov-owner@lists.openid.net<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > When replying, please edit your Subject line so it is more specific<o:p></o:p></p>
<p class="MsoPlainText"> > than "Re: Contents of Openid-specs-igov digest..."<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > Today's Topics:<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > 1. Tomorrow (Paul Grassi)<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > ----------------------------------------------------------------------<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > Message: 1<o:p></o:p></p>
<p class="MsoPlainText"> > Date: Tue, 19 Mar 2019 04:57:01 +0000<o:p></o:p></p>
<p class="MsoPlainText"> > From: Paul Grassi <pgrassi@easydynamics.com><o:p></o:p></p>
<p class="MsoPlainText"> > To: "openid-specs-igov@lists.openid.net"<o:p></o:p></p>
<p class="MsoPlainText"> > <openid-specs-igov@lists.openid.net><o:p></o:p></p>
<p class="MsoPlainText"> > Subject: [Openid-specs-igov] Tomorrow<o:p></o:p></p>
<p class="MsoPlainText"> > Message-ID: <ADF13F92-6D12-46C1-B409-71AA49D3E0AB@easydynamics.com><o:p></o:p></p>
<p class="MsoPlainText"> > Content-Type: text/plain; charset="utf-8"<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > All we have a new use case document in the repository to frame our next efforts. I know we have been slower to progress than other work groups, but we are using this draft use case doc as way to build momentum and speed release.
The document focuses on 2 primary uses cases:<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > * Attribute metadata ? A comment from the first ID that we agreed would be worked on in the next ?release?<o:p></o:p></p>
<p class="MsoPlainText"> > * Bi-directional relationships. ? This is a doosey, that may be broken into a few use cases, but essentially this is leveraging OIDC and OAuth to serve 2 functions. Oauth to protect an API (the API provider is the Auth Server)
and OIDC to federate to a website hosted by the API provider (the API provider is now a relying party, the API consumer is the OP).<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > I hope you all can start joining as we will have some fun defining these use cases in further detail.<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > Paul<o:p></o:p></p>
<p class="MsoPlainText"> > -------------- next part --------------<o:p></o:p></p>
<p class="MsoPlainText"> > An HTML attachment was scrubbed...<o:p></o:p></p>
<p class="MsoPlainText"> > URL: <http://lists.openid.net/pipermail/openid-specs-igov/attachments/20190319/57215e5c/attachment-0001.html><o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > ------------------------------<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > Subject: Digest Footer<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > _______________________________________________<o:p></o:p></p>
<p class="MsoPlainText"> > Openid-specs-igov mailing list<o:p></o:p></p>
<p class="MsoPlainText"> > Openid-specs-igov@lists.openid.net<o:p></o:p></p>
<p class="MsoPlainText"> > http://lists.openid.net/mailman/listinfo/openid-specs-igov<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > ------------------------------<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > End of Openid-specs-igov Digest, Vol 83, Issue 1<o:p></o:p></p>
<p class="MsoPlainText"> > ************************************************<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> ________________________________<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> This message is only for the use of the intended recipient and may contain information that is CONFIDENTIAL and PROPRIETARY to IDEMIA. If you are not the intended recipient, please erase all copies of the message and its attachments
and notify the sender immediately.<o:p></o:p></p>
<p class="MsoPlainText"> _______________________________________________<o:p></o:p></p>
<p class="MsoPlainText"> Openid-specs-igov mailing list<o:p></o:p></p>
<p class="MsoPlainText"> Openid-specs-igov@lists.openid.net<o:p></o:p></p>
<p class="MsoPlainText"> http://lists.openid.net/mailman/listinfo/openid-specs-igov<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
</div>
</body>
</html>