Features

With the _features.conf you can control which wallet API features are enabled. They are managed via the feature manager.

Available Features

Base Features
Please note that the base features should always be enabled to make full use of the wallet API.

  • web - Web service
  • wallet-service - Wallet service implementation
  • db - Database manager
  • logins - Logins method management
  • auth - Base authentication system

Optional Features

  • key-generation-defaults - Key generation defaults (key backend & generation config) configuration
  • registration-defaults - Registration defaults (key, DID) configuration
  • oidc - OIDC login feature
  • healthchecks - Enables healthcheck endpoints.
  • debug-endpoints - Enables various debug endpoints.
  • feature-flag-information-endpoint - Enables endpoints related to showing information about available features on this service instance.
  • runtime - Runtime mock provider configuration
  • push - Push notifications
  • external-signature-endpoints - Receive and present credentials using externally generated signatures. This is only required if keys are stored outside the Wallet API system. By default, keys are managed within the Wallet API, including those handled through our supported KMS integrations.
  • trusted-ca - allows JWTs signed with a trusted X509 certificate (X5C-JWS-Header) to authenticate wallet accounts.

Please note that the features listed below are accessible via the manager. However, as they are still under development, we advise against using them at this time.

  • trust - Trust records
  • rejectionreason - Rejection reasons use case
  • notification - Notification dispatch use case
  • tenant - Cloud-based tenant management

Example Setup

_features.conf
enabledFeatures = []
disabledFeatures = [
    debug-endpoints,
    healthchecks
]
Present a Digital Credential (W3C, SD-JWT VC) via OID4VP using External SignaturesDB