Unexpected reproducible behavior of PermitValue rule of type ScopeRegex in Shibboleth SP 3.4.1

[Florian Lengyel]

Pardon me, but when I see something like this, I investigate. The attribute-policy.xml wasn't working as expected.
I understand the scopes I might get. The only valid ones match the more restrictive pattern.
You're welcome to join a Zoom meeting with me to go over it. Or I can send you my complete configuration.
It's pretty vanilla. It's up to you--if it were me, I would at least verify the behavior and document it.
Or remove regular expressions--standard and well-understood in computer science--if you feel that way about them
Anyway if you have time, I'm willing to go over this.

F

* This email originates from a sender outside of CUNY. Verify the sender before replying or clicking on links and attachments. *

> OK, it is what it is. Fine--it's not a show-stopper.

To restate something said in a side discussion:  If you can you'd be very well off just using straight string comparison here - I assume you understand all the scopes you might get.

You obviously speak regexp better than I, but I maintain that regexps are usually a gun&bullet in search of a foot to shoot.

R

--
For Consortium Member technical support, see https://urldefense.com/v3/__https://shibboleth.atlassian.net/wiki/x/ZYEpPw__;!!PxiZbSOawA!PiddKmnqSSi9sI1HsT7JfY2wA59JW7yRHyI-O_V__H03N3A2W9EiZIwpXujNz5xSVvfVZ3yzYF3rL2jYplzEBN2w$
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net