Exporting SP attribute policy decisions to the application

Scott Cantor scott at restingparrotsoftware.com
Fri Nov 7 14:24:52 UTC 2025


I guess what I would say in general is that your option 1 is probably the right one for a testing service.

Most people don't do much filtering, and if all you're talking about is checking affiliation values and scopes, which is all the SP really does for most people, I'd do it in your testing harness.

And at least with V4, getting info out of the metadata and supplying it to the Agent as an Attribute is pretty simple to do.

Forget V3, it's a non-starter to even discuss anything there. I'm not touching that code going forward except for 2 reasons:

- adding deprecation warnings
- dependency-driven problems or changes
- security issues

It's feature frozen, which I will officially state somewhere when I get around to it.

-- Scott



More information about the users mailing list