Skip to content
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

Localization problem in ClientMessages #1103

Open
ichavchavadze opened this issue Apr 12, 2024 · 0 comments
Open

Localization problem in ClientMessages #1103

ichavchavadze opened this issue Apr 12, 2024 · 0 comments
Labels
bug Something isn't working
Projects

Comments

@ichavchavadze
Copy link
Collaborator

After a successful login, locale is set by cookies for 1 year. And if there was no login (anonymous authentication) - the locale is not set, we stay under the same user (e.g. admin), but cookies are not overwritten, although the locale may have changed.
Texts from ClientMessages are shown for example in date picker.

Possible solution by Alex:

Well, I see one clean option here so far.
Make an event when user locale changes to record the time and deny all tokens before that time during authentication.
Or store locale in token and compare locale during authentication and reject if different.
But the question is how critical the problem is.

Now workaround is relogin after changing locale on the server.

@ichavchavadze ichavchavadze added the bug Something isn't working label Apr 12, 2024
@ichavchavadze ichavchavadze added this to New in lsfusion via automation Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
lsfusion
  
New
Development

No branches or pull requests

1 participant