frappe / frappe/central

Datum token rotation is not happening right now

Open
#286 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
Python
Stars
18
Forks
11
Avg merge
1d 8h
Merged PRs (30d)
20

Description

- With Datum as the metric/log service manager, central mints out 2 tokens - datum metric token, and datum log token
- The expiry of these 2 JWTs are 7 days.
- [Line](https://github.com/frappe/central/blob/79747dae48883f0676f30a0ffb08c75f89e851c6/central/sso.py#L18) says that pilot will refetch the tokens when its near expiry.
- But currently there are no implementation of that in pilot side.
- We need a way for the token consumers to refetch/renew the tokens or make the tokens long lived.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with central/sso.py at the referenced line and trace how Datum metric and log JWTs are consumed by pilot. Decide whether consumers should refetch tokens near the seven-day expiry or use long-lived tokens; done means both tokens are renewed or remain valid without manual intervention.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
authentication, backend, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.