You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, SamlClient.fromMetadata takes a single samlBinding and uses it to both resolve the IDP endpoint and to populate the ProtocolBinding parameter in the AuthnRequest. But I should be able to set these up independently.
The text was updated successfully, but these errors were encountered:
Currently, I'm having to do a horrible hack to workaround this and #25 :
// check if SAML request starts with XML declaration: Base64("<?x") = "PD94"
// which means it's not compressed
if(samlRequest.startsWith("PD94")) {
String rawStr = EncodingUtils.decodeB64(samlRequest);
// this code needs to be reorganized if saml-client fixes #25 and doesn't fix #26
rawStr = rawStr.replace("urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect",
"urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST");
byte[] raw = rawStr.getBytes(StandardCharsets.UTF_8);
byte[] compressed = CompressionUtils.compress(raw, new Deflater(Deflater.DEFLATED, true));
samlRequest = EncodingUtils.encodeB64(compressed);
}
Currently, SamlClient.fromMetadata takes a single samlBinding and uses it to both resolve the IDP endpoint and to populate the ProtocolBinding parameter in the AuthnRequest. But I should be able to set these up independently.
The text was updated successfully, but these errors were encountered: