corda.cryptoLibrary

Configuration schema for the crypto library subsection.

  • busProcessors - Settings for crypto messages processors
    • flow - Settings for crypto flow ops messages processor
      • maxAttempts - Maximum attempts to process a message
        Default value: 3
      • waitBetweenMills - Time between attempts in milliseconds, if the number of values is less than attempts then the last item is repeated
        Default value: 200
    • ops - Settings for crypto ops messages processor
      • maxAttempts - Maximum attempts to process a message
        Default value: 3
      • waitBetweenMills - Time between attempts in milliseconds, if the number of values is less than attempts then the last item is repeated
        Default value: 200
    • registration - Settings for HSM registration messages processor
      • maxAttempts - Maximum attempts to process a message
        Default value: 3
      • waitBetweenMills - Time between attempts in milliseconds, if the number of values is less than attempts then the last item is repeated
        Default value: 200
  • cryptoConnectionFactory - Settings for database connections factory's cache of EntityManagerFactory(s)
    • expireAfterAccessMins - Expiration time in minutes for cached EntityManagerFactory
      Default value: 5
    • maximumSize - Maximum number of cached EntityManagerFactory
      Default value: 3
  • hsmMap - Settings for all available HSMs
    • hsmService - Settings for HSMService
      • downstreamMaxAttempts - Number of attempts to call downstream services to ensure consistency when assigning an HSM
        Default value: 3
    • signingService - Settings for SigningService
      • cache - Settings for key metadata cache
        • expireAfterAccessMins - Expiration time in minutes for cached key metadata
          Default value: 10000
        • maximumSize - Maximum number of cached key metadata
          Default value: 60

    Was this page helpful?

    Thanks for your feedback!

    Chat with us

    Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

    Propose documentation improvements directly

    Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.

    We're sorry this page wasn't helpful. Let us know how we can make it better!

    Chat with us

    Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

    Create an issue

    Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.

    Propose documentation improvements directly

    Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.