danslo Comments - Answer Overflow

danslo

•Created by danslo on 1/31/2025 in #💻┃support

Some users are are reporting issues signing in.

The other user says he sees the message "Something went wrong when we tried to authenticate you, and we can’t offer a quick way out. Start a new session and try signing in again. Error code: 8809"

12 replies

KKinde

•Created by danslo on 1/31/2025 in #💻┃support

Some users are are reporting issues signing in.

12 replies

KKinde

•Created by danslo on 1/31/2025 in #💻┃support

Some users are are reporting issues signing in.

One user says these spin indefinitely (this was the roast/mixed user):

12 replies

KKinde

•Created by danslo on 1/31/2025 in #💻┃support

Some users are are reporting issues signing in.

https://dashboard.sansec.io/

12 replies

KKinde

•Created by danslo on 1/31/2025 in #💻┃support

Some users are are reporting issues signing in.

yes it appears to be persistent, they're simply unable to login with Brave. when changing browsers (firefox), it does work

12 replies

KKinde

•Created by danslo on 1/31/2025 in #💻┃support

Some users are are reporting issues signing in.

Thank you. For what it's worth, I cannot reproduce it in Brave either 🤷‍♂️

12 replies

KKinde

•Created by danslo on 1/31/2025 in #💻┃support

Some users are are reporting issues signing in.

One of these brave users reports the following in console: verifyCustomUiElements.js:4 [Kinde] 🚨 No entry point found. Recommend using [data-kinde-root] to set an SPA entry point formSubmit.js:73 POST https://sansec.kinde.com/end_user_pages/widgets/partials/sign_up_sign_in/credentials_form net::ERR_ABORTED 401 (Unauthorized) responseMixed.js:232 Unknown response content-type. Received: text/plain; charset=utf-8. Expected: roast/mixed

12 replies

KKinde

•Created by danslo on 1/31/2025 in #💻┃support

Some users are are reporting issues signing in.

Looks like these users are using Brave. Are the Kinde team aware of any issues with this browser?

12 replies

KKinde

•Created by danslo on 11/26/2024 in #💻┃support

Given a low enough ID token expiry, is it safe to store it in the browser (localstorage/cookies)?

Thanks that's all I needed!

10 replies

KKinde

•Created by danslo on 11/26/2024 in #💻┃support

Given a low enough ID token expiry, is it safe to store it in the browser (localstorage/cookies)?

Expiration of token as well as cookie is low (3600s)

10 replies

KKinde

•Created by danslo on 11/26/2024 in #💻┃support

Given a low enough ID token expiry, is it safe to store it in the browser (localstorage/cookies)?

>What is your goal with storing the ID token in the browser? Are you using it primarily for frontend-only authentication, or will you also interact with a backend API? Interacting with server-side-rendered application (Go), which I don't want to complicate with sessions. >Which SDK or framework are you using? No SDK or framework, plain Go. >Are you handling user authentication solely through the ID token, or are you using access tokens as well? Currently storing ID token in cookie and validating in the backend (through middleware) on every request.

10 replies

KKinde

•Created by danslo on 11/26/2024 in #💻┃support

Given a low enough ID token expiry, is it safe to store it in the browser (localstorage/cookies)?

it's fine (in fact; desirable) to force them out after 3600s

10 replies

KKinde

•Created by danslo on 11/26/2024 in #💻┃support

Given a low enough ID token expiry, is it safe to store it in the browser (localstorage/cookies)?

I don't need my users to stay logged in either

10 replies

KKinde