Difference between revisions of "Mobile Driver's License with OIDC"
From MgmtWiki
(→Full Title) |
(→Context) |
||
| Line 4: | Line 4: | ||
==Context== | ==Context== | ||
* If the mDL reader receives the token and URL from the mDL, either during device engagement or device data retrieval, it may retrieve mDL data from the issuing authority via the Internet or locally. If the read chooses to use the internet, either OIDC or WebAPI can be used to retrieve the information. | * If the mDL reader receives the token and URL from the mDL, either during device engagement or device data retrieval, it may retrieve mDL data from the issuing authority via the Internet or locally. If the read chooses to use the internet, either OIDC or WebAPI can be used to retrieve the information. | ||
| + | |||
| + | ==Problems== | ||
| + | |||
| + | ==Soltuions== | ||
| + | * The transaction has been designed such that it is not necessary for the mDL holder to physically hand over the mobile device to the mDL verifier. | ||
==References== | ==References== | ||
Revision as of 14:43, 21 May 2021
Full Title
How to use OpenID Connect (OIDC) with a Mobile Driver's License (mDL) compliant with ISO 18013-5,
Context
- If the mDL reader receives the token and URL from the mDL, either during device engagement or device data retrieval, it may retrieve mDL data from the issuing authority via the Internet or locally. If the read chooses to use the internet, either OIDC or WebAPI can be used to retrieve the information.
Problems
Soltuions
- The transaction has been designed such that it is not necessary for the mDL holder to physically hand over the mobile device to the mDL verifier.
