LogoLogo
ProductsCommunityGitHubShare Feedback
Apps
Apps
  • Getting Started
  • Solutions
    • Web Wallet
      • Quick Start
      • Try it out!
      • Full Guide
        • Source code
        • Docker images
      • Authentication
      • Functions
      • Architecture
      • Configurations
        • Host
        • Credentials
        • Tokens
        • Storage
    • Verifier Portal
    • Issuer Portal
  • Community
    • Discord
    • Twitter
    • Newsletter
    • GitHub Discussions
  • DEVELOPER RELATIONS
    • Contribute
    • Roadmap
    • Share Feedback
    • Contact
  • Product Editions
    • Open Source | Always Free
    • Enterprise | Self-Managed
    • Cloud Platform | Managed
Powered by GitBook
On this page
  • Wallet configuration
  • Push notifications configuration

Was this helpful?

Export as PDF
  1. Solutions
  2. Web Wallet
  3. Configurations

Credentials

PreviousHostNextTokens

Last updated 1 year ago

Was this helpful?

Credential configurations set up the environment for functions related to authorization, credential, DID and key management. Currently, the following configurations are available:

Wallet configuration

specifies the remote location which web-wallet backend should use to proxy all the credential management, key management, DID management and authentication requests to. The configuration is stored in the wallet.conf file.

e.g. wallet configuration

remoteWallet = "https://wallet.walt.id"

Push notifications configuration

A push notifications service can be configured so that the end-user will receive notifications for both when they receive a credential accept request or a verification request. The configuration is stored in the push.conf file.

e.g. push notifications configuration

pushPrivateKey="{server-private-key}"
pushPublicKey="{server-public-key}"
pushSubject="mailto:dev@walt.id"
wallet configuration
push notifications configuration