DataSealer dependencies

[Nate Klingenstein]

> I don't know if CAS has limitations on ticket size, but I would say that continuing to use it long term implies that it be re-implemented using encrypted tickets to recover the state rather than as references. If we had to keep supporting SAML artifacts widely, I would be defining a new artifact type to allow for that.


I’m sure you could serialize something as long as the clients treat the ticket as a completely opaque string.  Is there any value in standardizing that?

It smells like OAuth: the only way to break the standard is to interoperate.