Unprotected realm not working as expected

Products

• SITEMINDER

Issue/Introduction

Customer has a realm in which /content/* is protected.  Customer has created an unprotected realm for /content/subcontent/*, but requests for this resource are unexpectedly protected.   

 

Environment

Release : ALL

Cause

The unprotected realm resource filter contained an asterisk, but this character is interpreted literally in a realm resource filter rather than being interpreted as a wildcard.  This resulted in no requests matching the unprotected realm.

Resolution

The non-working realm resource filter was:
qa-myhome_AgentGroup/content/subcontent*

The policy server began matching requests to this realm as expected when the realm resource filter was changed to:
qa-myhome_AgentGroup/content/subcontent

Additional Information

Wildcards are valid in rule resource filters, but not realm resource filters.  A * wildcard is always implied at the end of any realm resource filter.