Conditional - in relying party

[Lalith Jayaweera]

Also on another note, the default values for the relying partyI see in 2.4
series below

                                 signResponses="never"
signAssertions="always"
                                 encryptAssertions="conditional"
encryptNameIds="never"
                                 includeConditionsNotBefore="true"/>

is different to 3.3.x default values listed below ?



•signResponsesPredicate = *alwaysTrue*
•encryptAssertionsPredicate = alwaysTrue
•encryptNameIDsPredicate = alwaysFalse
•encryptAttributesPredicate = alwaysFalse


On Tue, Jun 27, 2017 at 12:05 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 6/26/17, 2:48 AM, "users on behalf of Lalith Jayaweera" <
> users-bounces at shibboleth.net on behalf of ljayaweera at gmail.com> wrote:
>
> > In the new IdP 3.x, what exactly below mapps to
> >
> >
> > signResponses="conditional" which was in 2.4.x
> >
> > All I can see is true or false
>
> It isn't something you should need to set since that's the default in the
> applicable cases. You're not seeing true or false, the fields are actually
> Predicates. True/false are just auto-mapped to predicate objects by Spring
> that always return those values. The "conditional" setting in the legacy
> relying-party file is implemented through a Java class that implements that
> logic and while I could go look it up, as I said you shouldn't need it.
> Just don't set the property.
>
> -- Scott
>
>
>
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170627/7374587e/attachment.html>