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

Improve support for KonText's ucnk_token_auth #1056

Open
tomachalek opened this issue Oct 24, 2022 · 0 comments
Open

Improve support for KonText's ucnk_token_auth #1056

tomachalek opened this issue Oct 24, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@tomachalek
Copy link
Member

In short - we should be able to handle refreshing session ID automatically in case the ID expires.
Here is the scenario:

  1. WaG client-side sends an AJAX request to KonText with X-Api-Token (= session ID generated using a private token)
  2. KonText finds out that the session ID is expired and responses with 401 Unauthorized.
  3. WaG client-side calls a special WaG server action refresh_session
  4. The refresh_session action will call KonText's /token/authenticate (it means that the WaG server must have a secret token stored in its config) and obtains a new session ID from KonText
  5. once WaG client-side gets a proper response, WaG will reload respective tiles (or the whole page in case this would be too cumbersome)
@tomachalek tomachalek added the enhancement New feature or request label Oct 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants