4 ms·
{ "pay": { "msg": "There are also other options.", "alg": "ES256", "iat": 1748248973, "tmb": "9PcBWntvjAktwfiPp8WxgOyQOwc1h6
by Zamicol 1y ago
{
"pay": {
"msg": "There are also other options.",
"alg": "ES256",
"iat": 1748248973,
"tmb": "9PcBWntvjAktwfiPp8WxgOyQOwc1h6Lo1UnB_gkWXKk",
"typ": "cyphr.me/msg/create"
},
"sig": "sHyMrykhsta5etjqH1e5oho0EpEs2FrblQ0DFHQo0aMgKd2V__SQ2Fl2EOSKt8wl65iLmKgIaMVEgCmhtvbUcg"
}
Verify: https://cozejson.com https://cozejson.com
Spec: https://github.com/Cyphrme/Coze https://github.com/Cyphrme/Coze
- hirsin 1y agoHm, I wonder how the double sig problem that SAML would run into will work here. What happens if someone adds an extra sig object there?
- francislavoie 1y agoI don't like it much, using JSON as the transport has some problems if encoded in a URL as required by many auth flows. Paseto encodes the whole version+payload+signature to make it easier to transport. Of course you could just base64 encode the whole Coze JSON, but that isn't part of the spec, which means the spec is weak.