Silent Redirect URI vs Silent Login URI

This is actually more a question than an issue: For some reason, the method silentLoginAsync is timing out on my project. I’m trying to figure out why.

Looking at the code and instructions, it’s not clear to me what those two params are used for.

silent_login_uri what value should I add here? Is it a URL from my site? or is it something from my authentication provider?

Do you guys have any idea why this might be timing out?

Attaching a screenshot of the issue happening in production.

[guillaume-chervet]

Hi, @tielushko ,

By default the library use the shorter life between access_token and id_token.

There is a property to change the default behavior.

an example: https://github.com/AxaGuilDEv/ml-cli/blob/master/src/Ml.Cli.WebApp/ClientApp/public/environment.dev.json "token_renew_mode": "access_token_invalid"

token_renew_mode: PropTypes.string, // Optional, update tokens base on the selected token(s) lifetime: "access_token_or_id_token_invalid" (default), "access_token_invalid" , "id_token_invalid"

[tielushko]

I wanted to add to this conversation, we have set the AccessTokenLifetime property on the IdentityServer that we use with this application to a lifetime of 48hrs. However, I noticed that the expiresAt property is different and is always set to be 300 seconds from the time the token was issued, despite the expiresIn property being valid, and set to 48hrs (172800 seconds).

How would we go about modifying this expiresAt property? I see it used in codebase quite frequently and I believe that, in part, triggers our silent sign in failures.

Additionally, I checked the cookie that the OIDC uses, and it has the SameSite=None property.