PreRequestedAttribute in ExternalIntercept

[B]

Thanks. The MFA example has

resCtx.resolveAttributes(custom);

which is not resolvable in our JSP.

Should we code it differently, or does this imply creation of another AttributeResolver service ("custom") and its registration in services.xml?

On Thu, May 7, 2026 at 11:58, Scott Cantor via users <[users at shibboleth.net](mailto:On Thu, May 7, 2026 at 11:58, Scott Cantor via users <<a href=)> wrote:

>> We configured the AttributeDefinition with 'preRequested="true"'.
>
> That has nothing to do with your use case. "Pre-requesting" in the resolver refers to a preliminary resolution step that happens when standard resolution does, it's just so the resolver's own activation conditions can reference them.
>
> Any other use cases for attribute resolution require explicitly coded/scripted use of the resolver service in other ways/places, as in the MFA flow examples or other similar cases.
>
> -- Scott
>
> --
> For Consortium Member technical support, see https://shibboleth.atlassian.net/wiki/x/ZYEpPw
> 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/20260507/c275c8bf/attachment.htm>