You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 29, 2024. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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 toundefined
as per code here.This is contrary to intended behaviour because the
createDidAuthResponseToken
method of theDidAuthClientService
does accept anoptions
arguments which containsmaxTokenValidInMs
i.e. the intended expiry of theresponseToken
, 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.
The text was updated successfully, but these errors were encountered: