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 Mar 3, 2022. It is now read-only.
we currently facing the problem, that the silent renew is going to not working after about 30min. We were able to determine that the SubjectId is missing on IS4.
When looking into the network tab in chrome for the client requests, the following order is visible:
authentication request
silent renew request
user info request
Step three is missing before the next authentication request and due to that the SubjectId / id_token, I guess.
Our access-token lifetime is 1 h, identity-token lifetime is 5 min. For testing purpose we set the silent renew to trigger every 4 min.
We are using the oidc-client-js@1.4.1 in combination with the redux-oidc lib.
Is there anything we forget in our configuration on client / server side?
Thanks a lot.
The text was updated successfully, but these errors were encountered:
Hi @brockallen ,
yes we are using asp.net identity. I will check the cookie with the backend guy. Thanks for the hint. I will come back with more information.
Hi,
at first thanks for the great library 馃槂
we currently facing the problem, that the silent renew is going to not working after about 30min. We were able to determine that the SubjectId is missing on IS4.
When looking into the network tab in chrome for the client requests, the following order is visible:
Step three is missing before the next authentication request and due to that the SubjectId / id_token, I guess.
Our access-token lifetime is 1 h, identity-token lifetime is 5 min. For testing purpose we set the silent renew to trigger every 4 min.
We are using the oidc-client-js@1.4.1 in combination with the redux-oidc lib.
Is there anything we forget in our configuration on client / server side?
Thanks a lot.
The text was updated successfully, but these errors were encountered: