... > % RXGK_COMPOUND_IDENTITY, "Token's combined identity not usable" > > The server doesn't like the compound identity presented by the client > solely because it is a compound identity (as opposed to a single-identity > token) or the structure of the compound identity is too complicated to be > used as input for CombineTokens. (This one is rather speculative.)
This will be a fun error to get. > % RXGK_PRINTED, "Printed token not allowed" > > The client presented a token that was printed, but such tokens are not > allowed for that use case by the server. E.g., AFSCombineTokens (in the > rxgk-afs draft) explicitly MUST NOT accept printed tokens. On the other > hand, we don't talk about printed tokens in this document at all, so > maybe this error code should be deferred. I assume printed tokens are something pre-generated, perhaps for processing batch jobs? I'd say if you are going to include this error, we'd need a brief definition of printed tokens. -- Michael Meffie <[email protected]> _______________________________________________ AFS3-standardization mailing list [email protected] http://lists.openafs.org/mailman/listinfo/afs3-standardization
