mace-opensaml-users - Re: Very minor problem with SAML2ArtifactType0004
Subject: OpenSAML user discussion
List archive
- From: Chad La Joie <>
- To:
- Subject: Re: Very minor problem with SAML2ArtifactType0004
- Date: Tue, 20 Mar 2007 21:01:35 -0400
- Organization: University Information Systems
Thanks Jeff, it has been corrected.
Jeff Brewer wrote:
Here is the top of the parseArtifact method of SAML2ArtifactType0004. It seems to always throw an exception “Illegal artifact type code” when the type code is correct (0004 for this artifact type). The Arrays./equals/(typeCode, /TYPE_CODE/) should be !Arrays./equals/(typeCode, /TYPE_CODE/) then throw the exception. It would be nice if this made it into svn. I think all the SAML1ArtifactTypes have the same problem.
*public* *static* SAML2ArtifactType0004 parseArtifact(*byte*[] artifact) *throws* IllegalArgumentException {
*if* (artifact.length != 44) {
*throw* *new* IllegalArgumentException("Artifact length must be 44 bytes it was " + artifact.length + "bytes");
}
*byte*[] typeCode = { artifact[0], artifact[1] };
// This code should be !Arrays./equals/(typeCode, /TYPE_CODE/)
*if* (Arrays./equals/(typeCode, /TYPE_CODE/)) {
*throw* *new* IllegalArgumentException("Illegal artifact type code");
}
Jeff Brewer
PayCycle, Inc.
--
Chad La Joie 2052-C Harris Bldg
OIS-Middleware 202.687.0124
- Very minor problem with SAML2ArtifactType0004, Jeff Brewer, 03/20/2007
- Re: Very minor problem with SAML2ArtifactType0004, Chad La Joie, 03/20/2007
Archive powered by MHonArc 2.6.16.