Configuring User to User Delegation
In order to use the user to user delegation feature, the wallet server needs to be configured. As configuration prerequisites for user to user delegation, both parties involved in the flow must be wallet account owners and must be able to share connection invite.
Wallet Server Configuration
Parameters
Parameter | Description | Accepted Value |
---|---|---|
user-led-delegation.invitationExpiryInSeconds | The duration after which the connection invite expires | Numerical Value in Seconds (Defaults to 3600 ) |
user-led-delegation.connectionExpiryInSeconds | The duration after which the delegate connection expires | Numerical Value in Seconds (Defaults to 3600 ) |
user-led-delegation.invitationEndpoint | The valid endpoint the first user has to send to the second user | /me/delegate-connection-invitations/invite-response (Defaults to /me/delegate-connection-invitations/invite-response ) |
user-led-delegation.host | The wallet server host | https://wallet.dev.identos.ca (Defaults to Unspecified ) |
user-led-delegation.delegation-restriction-mode | The sensitive resource restriction mode | permissive or restrictive (Defaults to restrictive ) |
Below is a sample Wallet Server configuration file that, apart from the general wallet server configuration, includes the parameters required for user to user delegation (highlighted section).
Sample Configuration
Sample Configuration section of application.yml for Wallet Server to configure User-Led Delegation
## Tomcat Server Configuration
user-led-delegation:
invitationExpiryInSeconds: 3600 #value in seconds
connectionExpiryInSeconds: 3600 #value in seconds
invitationEndpoint: /me/delegate-connection-invitations/invite-response
host: ${server-host}
delegation-restriction-mode: restrictive # can be set to restrictive or permissive