Superset showing error "not authorized" after Integrating with key clock

[shafad1]

I have configured openid for keyclock integration .. login is happening and session is generating at the keyclock side after that while trying to authenticate with superset getting the message 'not authorized' in browser and getting error log as invalid token

error :
2023-11-06 19:16:09,291:INFO:oauth2client.client:Successfully retrieved access token
2023-11-06 19:16:09,292:ERROR:flask_oidc:Token issued in the past
2023-11-06 19:16:09,292:DEBUG:flask_oidc:Invalid ID token
2023-11-06 19:16:09,293:INFO:werkzeug:10.81.233.98 - - [06/Nov/2023 19:16:09] "GET /oidc_callback?state=eyJjc3JmX3Rva2VuIjogIktSZzFKVWVwRU5hUWRWTFlHVDA4ZVRTRG9zc29sdjV1IiwgImRlc3RpbmF0aW9uIjogImV5SmhiR2NpT2lKSVV6VXhNaUo5LkltaDBkSEE2THk4eE1DNHdMakV3TGprNk9EQTRPQzlzYjJkcGJpOGkuZFZaTnhKWVUwdGlQVEVIcjFFdzlSakI3S2tkbXZyX0dOdTFDelkwMklFWmFkUURBSzlXalhYU0s0OV80a2dTZksyU2pkX0dmdnVmTV9OaEhDSXBCWkEifQ%3D%3D&session_state=fa3d40a6-6362-454d-b71a-824284bc5c5b&code=25b1986b-491f-4fec-9dbc-d8e06ca77810.fa3d40a6-6362-454d-b71a-824284bc5c5b.1346fbaa-e28c-4b68-be50-3fd282f8c0e2 HTTP/1.1" 401 -

Can anyone please help me on this ?

[Ralkion]

Token issued in the past

Could the issue be with the server clocks being in different time zones?

[rusackas]

Since it's been nearly 5 months with an unanswered diagnostic question, I'll assume OP moved on, and we can call this one stale.