corda.membership
Configuration schema for the membership subsection.
TTLs
- Maximum duration in minutes between to wait for a message to be sent (null to wait forever).declineRegistration
- Maximum duration in minutes between to wait for a decline registration message.
Default value: 8
Minimum value: 1
Maximum value: 1440membersPackageUpdate
- Maximum duration in minutes between to wait for a members package update message.
Default value: 10
Minimum value: 1
Maximum value: 1440updateToPendingAutoApproval
- Maximum duration in minutes between to wait for an update registration status to pending auto approval.
Default value: 3
Minimum value: 1
Maximum value: 1440verifyMemberRequest
- Maximum duration in minutes between to wait for a verify member request.
Default value: 20
Minimum value: 1
Maximum value: 1440
maxDurationBetweenSyncRequestsMinutes
- Maximum duration in minutes between member list synchronization requests.
Minimum value: 10
Maximum value: 2880
Default value: 480
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.