Some custom Seacat claims clash with officially registered claims (https://www.iana.org/assignments/jwt/jwt.xhtml).
Current state in Seacat Auth
psid claim contains "root" session ID
sid claim contains "client" Session ID
jti claim is not used
Proposal
sid is registered as "Session ID" for the purpose of SSO login and logout. In Seacat Auth this should correspond to the "root" session ID.
jti is registered as "JWToken ID" for the purpose of revoking the token, checking its uniqueness etc. This would have to be implemented.
- Introduce custom claim
csid (Client Session ID) to refer to the seacat client session id.
Some custom Seacat claims clash with officially registered claims (https://www.iana.org/assignments/jwt/jwt.xhtml).
Current state in Seacat Auth
psidclaim contains "root" session IDsidclaim contains "client" Session IDjticlaim is not usedProposal
sidis registered as "Session ID" for the purpose of SSO login and logout. In Seacat Auth this should correspond to the "root" session ID.jtiis registered as "JWToken ID" for the purpose of revoking the token, checking its uniqueness etc. This would have to be implemented.csid(Client Session ID) to refer to the seacat client session id.