-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Silent Redirect URI vs Silent Login URI #892
Comments
Hi @ronildo , silentlogin is used internally to manage silent callback route. It is not mandatory. On which browser do you see this error? |
I see this basically on all browsers, the screenshot was taken from Chrome. |
If oidc server is not in the same domain than your website then cookie should have attribute value: SameSite=None |
yes, oidc server is not in the same domain as the app. |
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. |
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
|
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.
The text was updated successfully, but these errors were encountered: