Defaults for encryption and signing predicates in SAML profiles

[Cantor, Scott]

On 4/29/14, 10:02 AM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:

>On 4/29/14, 5:01 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:
>
>>While I was adding the parse for encryptAttributes to the SAML2 profiles
>>I
>>realized that in porting the parsers over from V2 I was bring with them
>>the "defaulted in the setter" paradigm for the signing and encryption
>>predicates.  We are hoping to avoid this non-obvious behaviour and so by
>>way of an experiment I turned this off.
>
>I don't think we really can, because of compatibility, can we?

I think what we wanted to try and do, though, was make sure that instead
of the defaults being in the parsers, that we set them inside the profile
configuration objects themselves by installing the right predicates in
each case to match the current defaults.

What bugged me about V2 is that you had to look at the Spring parser to
find out the default for an object in practice, instead of just looking at
the object itself.

-- Scott