[Openid-specs-igov] Openid-specs-igov Digest, Vol 83, Issue 1

[Kelts, David]

Does #2 mean support for (multiple) Attribute Providers in that the OP could gather attributes from an API on behalf of the Digital Subject?

David
🌿Sent from my iPhone

> On Mar 20, 2019, at 8:00 AM, "openid-specs-igov-request at lists.openid.net" <openid-specs-igov-request at lists.openid.net> wrote:
>
> Send Openid-specs-igov mailing list submissions to
>    openid-specs-igov at lists.openid.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>    http://lists.openid.net/mailman/listinfo/openid-specs-igov
> or, via email, send a message with subject or body 'help' to
>    openid-specs-igov-request at lists.openid.net
>
> You can reach the person managing the list at
>    openid-specs-igov-owner at lists.openid.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Openid-specs-igov digest..."
>
>
> Today's Topics:
>
>   1. Tomorrow (Paul Grassi)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 19 Mar 2019 04:57:01 +0000
> From: Paul Grassi <pgrassi at easydynamics.com>
> To: "openid-specs-igov at lists.openid.net"
>    <openid-specs-igov at lists.openid.net>
> Subject: [Openid-specs-igov] Tomorrow
> Message-ID: <ADF13F92-6D12-46C1-B409-71AA49D3E0AB at easydynamics.com>
> Content-Type: text/plain; charset="utf-8"
>
> 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:
>
>
>  *   Attribute metadata ? A comment from the first ID that we agreed would be worked on in the next ?release?
>  *   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).
>
> I hope you all can start joining as we will have some fun defining these use cases in further detail.
>
> Paul
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.openid.net/pipermail/openid-specs-igov/attachments/20190319/57215e5c/attachment-0001.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Openid-specs-igov mailing list
> Openid-specs-igov at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-igov
>
>
> ------------------------------
>
> End of Openid-specs-igov Digest, Vol 83, Issue 1
> ************************************************
>

________________________________

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.