Skip to main content

9 posts tagged with "Developers"

View All Tags

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.

For developers. Two new features for EU Digital Identity verification, in the Hovi Connect API and the Cloud Wallet API:

  • Compound proof requests: ask for several credentials in a single request and choose how the requirements work together.
  • Transaction data: have the holder confirm details, such as a payment, as part of the proof request.

For everyone.

  • Passkeys: sign in to Hovi Studio with a passkey instead of a password.
  • Credential designs: upload your logo and background image from your computer when you design a credential template.

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

  • Revoke credentials: cancel an SD-JWT credential you issued, so verifiers see it is no longer valid. See Revoke a credential.
  • Authorization Code Flow: ask the holder to sign in before they receive the credential. See Issue a credential.
  • vc+sd-jwt credentials: a new SD-JWT credential format for templates and verification.

For everyone. In Hovi Studio you can now add your brand to the pages and emails people see when they receive a credential.

For everyone. Hovi now supports Microsoft Entra Verified ID:

Also in this release:

  • Organizational wallets: your organization can receive and hold credentials itself. See Organizational wallets.
  • "Tenant" is now "organization" everywhere in Hovi. Existing integrations keep working.