Resolve session from X-***-Token header in CallerSessionResolver

FixSecurityService
Ya
7 Julai 2026, 23:48 UTC
Mwandishi
Kamo
Ahadi ya
0e62afe

The kamo-internal -> APIService BFF path forwards the session as the X-***-Token header, but the resolver only read the X-OTK attribute or the *** cookie — so BaseLosController endpoints (incl. the new KamoDesktop SSO) got no session and 401'd. Add the header as a source (OTK attr -> X-***-Token header -> *** cookie).

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei