Signing Assertion with SHA256
Yang, Gang CTR (US)
gang.yang.ctr at mail.mil
Thu Jan 16 09:40:20 EST 2014
Thanks, Brent. This is what I ended up doing right after the bootstrap and it worked.
Gang
________________________________________
From: dev-bounces at shibboleth.net [dev-bounces at shibboleth.net] on behalf of Brent Putman [putmanb at georgetown.edu]
Sent: Wednesday, January 15, 2014 9:27 PM
To: dev at shibboleth.net
Subject: Re: Signing Assertion with SHA256
On 1/13/14 2:00 PM, Yang, Gang CTR (US) wrote:
>
> I also found some posts that mentioned SecurityConfiguration class, which contains the security parameters including the reference digest method. However, this a read-only interface and I can't seem to change anything. I'm wondering what's the right interface or class in OpenAM to programmatically change the configuration. This way may be more general than changing each ContentReference instance's settings. Would appreciate if any one can provide any pointer on this.
>
Realized I never answered this...
Yes, the Configuration instance holds an instance defined by the
SecurityConfiguration interface, which has only accessor methods. But
in reality there is only impl of that interface,
BasicSecurityConfiguration in the same package, and it has setter
methods. In v2 OpenSAML the instance will always be of that type,
although you should of course check before casting.
Changing the signatureReferenceDigestMethod property there is a global
change and will cause all SAMLContentReferences to use the specified
algorithm.
--
To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net
More information about the dev
mailing list