On 18/02/13 16:54, John Bradley wrote:
A base64url decoder doesn't need the padding bytes in this case. They are
really only useful if you are concatenating outputs together. The number of
missing pads characters can be calculated from the number of base64url encoded
octets to be decoded.
A base64url decoder doesn't need the padding bytes in this case. They are
really only useful if you are concatenating outputs together. The number of
missing pads characters can be calculated from the number of base64url encoded
octets to be decoded.
So the padding and any other line wraps S
Hi,
RFC4648 [1] says:
"The pad character "=" is typically percent-encoded when used in an
URI [9], but if the data length is known implicitly, this can be
avoided by skipping the padding; see section 3.2."
while the SAML2 Bearer token draft says:
"The SAML Assertion XML data MUST be encoded
