New CAS metadata support in 3.4

Paul B. Henson henson at
Tue Nov 27 15:36:52 EST 2018

> From: Marvin Addison
> Sent: Tuesday, November 27, 2018 4:57 AM
> Yes. The entity ID is simply a unique identifier, but the CAS protocol
> machinery carries around the exact service URL passed to it by the
> client, which can vary dramatically based on specific usage scenarios.

Ah; so the current best practice then would be to use an attribute release policy controlled by regex with the same regex that would've been used in cas-protocol.xml to define the service? That might warrant a bullet point on the documentation page :).

> appropriate for 4.0. It might turn out to be a minor change, but I
> can't say either way without taking the time to analyze and map out a
> plan. Would you mind filing an improvement issue for that?

Sure thing, IDP-1367.

Thanks much, and thanks also to Scott for his feedback on this question.

Paul B. Henson  |  (909) 979-6361  |
Operating Systems and Network Analyst  |  henson at
California State Polytechnic University  |  Pomona CA 91768

More information about the users mailing list