About • Contributing • Usage • Licensing
This repository is created to align the implementation of digital wallets across the EWC LSP consortium wallet providers. This also ensures all wallets providers can self-test and sign off against the EWC Interoperability Test Bed (ITB).
Feel free to improve the plugin and send us a pull request. If you find any problems, please create an issue in this repo. Wallet providers can raise a PR once they have implemented and aligned with the RFCs.
eudi-wallet-oidc-ios is available through SPM. To install it, simply add the following spm repository url https://github.com/decentralised-dataexchange/eudi-wallet-oidc-ios to your project package dependencies.
| Function | Return Type | Description |
|---|---|---|
| createJWK() | [String: Any]? | Generate JWK of curve P-256 for an optional seed value. |
| createDID(jwk: [String: Any]) | String | Generate a did:key:jcs-pub decentralised identifier. |
| Function | Return Type | Description |
|---|---|---|
| resolveCredentialOffer(data: String?) | CredentialOffer | To process the credential offer request |
| processAuthorisationRequest(did: String, privateKey: P256.Signing.PrivateKey, credentialOffer: CredentialOffer, codeVerifier: String, authServer: AuthorisationServerWellKnownConfiguration) | String? | This API requests to grant access to the credential endpoint. Returns URL with short lived authorisation code in query parameter |
| processTokenRequest(authServerWellKnownConfig: AuthorisationServerWellKnownConfiguration, code: String, did: String, privateKey: P256.Signing.PrivateKey, codeVerifier: String, isPreAuthorisedCodeFlow: Bool, preAuthCode: String, userPin: String?) | TokenResponse | To obtain the access token |
| processCredentialRequest(did: String, privateKey: P256.Signing.PrivateKey, credentialOffer: CredentialOffer, credentialEndpointUrlString: String, c_nonce: String, accessToken: String) | CredentialResponse | To obtain the credential |
| processDeferredCredentialRequest(acceptanceToken: String, deferredCredentialEndPoint: String) | CredentialResponse | To obtain the credential issued in a deferred manner. |
| Function | Return Type | Description |
|---|---|---|
| processAuthorisationRequest(data: String?) | PresentationRequest? | Authorisation requests can be presented to the wallet by verifying in two ways: 1) by value 2) by reference as defined in JWT-Secured Authorization Request (JAR) via use of response_uri. The custom URL scheme for authorisation requests is openid4vp://. |
| sendVPToken(did: String, privateKey: P256.Signing.PrivateKey, presentationRequest: PresentationRequest?, credentialsList: [String]?) | Data? | Authorisation response is sent by constructing the vp_token and presentation_submission values. |
| Function | Return Type | Description |
|---|---|---|
| getIssuerConfig(credentialIssuerWellKnownURI: String?) | IssuerWellKnownConfiguration? | To resolve the well-known endpoint for the credential issuer |
| getAuthConfig(authorisationServerWellKnownURI:String?) | AuthorisationServerWellKnownConfiguration? | To resolve the well-known endpoint for the authorisation server |
| Function | Return Type | Description |
|---|---|---|
| generateCodeVerifier() | String? | To create code verifier (https://datatracker.ietf.org/doc/html/rfc7636#section-4.1) |
| generateCodeChallenge(codeVerifier: String) | String? | To generate code challenge from the code verifier (https://datatracker.ietf.org/doc/html/rfc7636#section-4.2) |
Refer the Issue Verifiable Credential RFC for issuance flow.
- The credential issuance can be an authorisation flow or a pre-authorised one.
- The credential offer can be obtained from QR code or Deeplink. Make use of
resolveCredentialOfferfor processing the credential offer - Perform the Discovery to get the Issuer config and Autherisation server config. Use
getIssuerConfigandgetAuthConfigfor it. - If the credential issuance is authorisaation flow then call the
processAuthorisationRequestand thenprocessTokenRequestusing the code received - If the credential issuance is pre-authorised, the call
processTokenRequest, show PIN entering screen and pass the PIN in the token request if PIN required in theCredential Offer - Fetch credential using the
processCredentialRequest, in response we get the credential. If the response containsacceptanceToken, then pollprocessDeferredCredentialRequestunitll the credential is received.
Refer the Present Verifiable Credentials RFC for Verification flow.
- The presentation request can be obtained fromQR code or Deeplink. Make use of
processAuthorisationRequestfor processing the presentationRequest. - Use
sendVPTokenfor verification.
Licensed under the Apache 2.0 License, Version 2.0 (the "License"); you may not use this file except in compliance with the License.
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the LICENSE for the specific language governing permissions and limitations under the License.