Upgrading to IdP 5 Deprecation Issues

Matt Brennan brennanma at gmail.com
Mon Jun 9 19:00:20 UTC 2025


Thanks for the reply. I feel like an idiot now for not just trying to
replace .apply() with .test() and see what happened.



On Mon, 2 Jun 2025 at 18:19, Cantor, Scott <cantor.2 at osu.edu> wrote:

> I can't speak to LDAP other than I know the general issue was that those
> were JNDI properties and we don't use JDNI anymore, ldaptive is its own
> LDAP client now. If there are native equivalents, they'd be documented by
> ldaptive if we don't have properties that automate them, and those should
> be documented in the wiki.
>
> > I see the ContextCheckInterceptConfiguration on the Wiki. I just
> > don't see how to implement it in this use case.
>
> I can promise that duplicating our flows is a very bad idea, but if you
> wrote your own and you're calling Predicate.apply(), just change the flow
> expression to call test() instead.
>
> But the built-in flow does anything you could likely need. Write a
> function in Javascript and it can call any number of Predicates you could
> possibly want however you want. If the Function always returns
> ContextCheckDenied if any  of them fail, that's the equivalent of the old
> flow. Or they can return different custom events so each condition is
> handled uniquely, which is the more advanced model.
>
> For members, I'll happily mock it all, but not here.
>
> -- Scott
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20250609/45ba613d/attachment.htm>


More information about the users mailing list