FWIW, the AnonymousRegisteredServiceUsernameAttributeProvider has nothing to do with your use case. Basically this component generates a random, opaque tokens (unique per registered service) and releases those values in place of real authenticated principal ids to CAS client apps.
In your case, you simply need not to protect your web application of interest by any CAS client “protection agent mechanism” e.g. CAS Java client library, Spring Security library [insert your CAS client library of choice here]. Hope this clears it up a bit. Best, Dmitriy. > On Feb 8, 2016, at 10:17 AM, William <[email protected]> wrote: > > Chris, > > I think that is what I will have to do. I was hoping there was a way to do > this without touching the CAS web.xml or Spring Security files. > > There is an > org.jasig.cas.services.AnonymousRegisteredServiceUsernameAttributeProvider > class. > > I think this provides anonymous access to a service, but I do not see much > documentation on how to configure it. > > Regards > > -- > You received this message because you are subscribed to the Google Groups > "CAS Community" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/ > <https://groups.google.com/a/apereo.org/group/cas-user/>. -- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/.
