Skip to main content

EU Digital Identity: issue credentials after sign-in with your own login

For developers. New for EU Digital Identity in the Hovi Connect API:

  • Your own sign-in system: connect your company or university login (any OAuth 2.0 or OpenID Connect identity provider) to an organization, and manage up to 5 per organization with the new authorization server endpoints. See Connect your own sign-in system.
  • Sign in, then receive the credential: with the authorization code flow, choose which server the holder signs in with for each offer, and fill details such as their name and email from the sign-in. See Issue a credential.
  • Your own credential scope: set credentialScope when you create a JSON-LD, SD-JWT or mDoc template. See Credential templates.

Breaking changes. If you use the authorization code flow:

  • Credential offers must now send authorizationCodeflowConfig.authorizationServerId. Hovi no longer uses your organization's first server by default.
  • authorizationCodeflowConfig.authorizationServerUrl is removed. Use authorizationServerId.
  • POST /organization/create no longer accepts authorizationServerConfigs. Servers you added that way can't be used in offers: add them again with the new endpoints.