[Openid-specs-ab] [E] OpenID Connect for Identity Proofing(Proposal)

[Tom Jones]

Their API is public, their processes are not. It is my understanding that
they do the lookup in the state databases directly. I cannot tell you
anything about that api.
This is becoming more interesting because the DHS 'Real ID law', which
mandates a certain level of proofing be be able to get on an airplane (or
certain other venues.)
My state already offers two levels of proofing (assurance if you will.)  I
can use my enhanced state driver's license as a stand-in for a passport and
visa to Canada.

Health is now the topic of most interest to me.  What sort of user consent
is required for each of about 6 different categories of data that could be
transferred between providers.
I think that you are going the wrong way with sending more data than is
required for the proofing process. Current history is not on your side.
Legally i have no information about what might be required.
Peace ..tom


On Thu, Feb 14, 2019 at 10:09 AM Torsten Lodderstedt <
torsten at lodderstedt.net> wrote:

>
> > Am 14.02.2019 um 17:47 schrieb Tom Jones <thomasclinganjones at gmail.com>:
> >
> > AAMVA validates the data provided to it by the client (from the user)
> against state issued identity documents
>
> I’m trying to understand the process. I assume the client sends a set of
> data to a AAMVA via an API. Does AAMVA look that data up in databases
> containing the data of state issued identity documents?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20190214/9728b128/attachment.html>