Page History

...

While I'm recommending we use the compressed serialization in order to minimize message size and minimize issues related to having to chunk overly large payloads, there are alternate ways of encapsulating the above in it's own JSON.

Here would be a JOSE complete message

{
  "version": "1", //Message format version
  "timestamp": "createtime of message",
  "sequence": "1", //message sequence number, integer, increments per-message
  "securityImplementation": "edu.internet2.middleware.grouperClient.messaging.security.JoseMessageSecurity",
  "payload": "eyJhbGciOiJFUzI1NiJ9.VGhpcyBpcyBzb21lIHR"
}

sdf

{ 

  "version": "1", //Message format version 

  "timestamp": "createtime of message", 

  "sequence": "1", //message sequence number, integer, increments per-message 

  "securityImplementation": "edu.internet2.middleware.grouperClient.messaging.security.JoseMessageSecurity", 

  "payload": "sdkj4h23kjh345lk3j9sd8f0a929s0df8s09df8s" 

}