[cas-dev] Specifying priority for wildcard URL's?

[Scott Battaglia]

Hugh,

If you guys are interested in this, please open a JIRA issue and we can try
and get it in for the 3.2.1 release.  We'll probably need your assistance
from a design perspective (and obviously anyone else's assistance who wants
to offer it ;-))

Thanks
-Scott

On Feb 5, 2008 4:25 PM, Hugh Eaves <hleaves at vcu.edu> wrote:

> Are there any plans to allow the specification of a "service priority"
> when
> looking up RegisteredService's by the service URL's? (i.e. calling
> ServicesManager.findServiceBy(service)) Right now, the
> DefaultServicesManager just returns the first service that matches from
> the
> registry. With the possibility of specifying wildcards for service URL's,
> there may actually be several RegisteredService's that match a given
> service
> URL.
>
> The reason I ask is that we'd like to use the service manager to define
> some
> fairly general "catch all" service URL's that only get a very limited set
> of
> attributes, and then override these general URL's with more specific URL's
> that are allowed to see more attributes.
>
> For example:
>
> Catch All URL: https://*.vcu.edu/**  <-- can only see userId, displayName
> More Specific URL: https://something.vcu.edu/** <-- can see userId,
> displayName, studentId, DOB, classification, etc.
>
>
> Thanks,
>
> Hugh Eaves
> Virginia Commonwealth University
> Technology Services / Portal Development
> (804) 828-2097
>
>
> _______________________________________________
> cas-dev mailing list
> cas-dev at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas-dev
>



-- 
-Scott Battaglia

LinkedIn: http://www.linkedin.com/in/scottbattaglia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas-dev/attachments/20080206/347ade92/attachment.html