Skip to content
This repository has been archived by the owner on Aug 29, 2024. It is now read-only.

DID-Auth: Client not setting expiry for responseToken #236

Open
d1vyansh6upta opened this issue Aug 23, 2022 · 0 comments
Open

DID-Auth: Client not setting expiry for responseToken #236

d1vyansh6upta opened this issue Aug 23, 2022 · 0 comments

Comments

@d1vyansh6upta
Copy link

As per the documentation here, the client should be able to configure the expiry of the responseToken, which is 12 hours by default.

However, as per the code implementation, the expiry for the responseToken is explicitly set to undefined as per code here.

This is contrary to intended behaviour because the createDidAuthResponseToken method of the DidAuthClientService does accept an options arguments which contains maxTokenValidInMs i.e. the intended expiry of the responseToken, but then does not actually set the expiry of the token as per this value.

Furthermore, the default expiry of 12 hours (as per the docs) too is not being set.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant