This could be accomplished by setting the ‘usernameAttribute’ property in the RegisteredService instance in question: http://jasig.github.io/cas/4.0.x/installation/Service-Management.html <http://jasig.github.io/cas/4.0.x/installation/Service-Management.html>
In CAS 4.1 this is even easier to do via a very flexible services management web app (with username attribute provider config options). Check this demo out: http://jasigcasmgmt.herokuapp.com/ <http://jasigcasmgmt.herokuapp.com/> and play with it by defining few registered services. You could login with casuser/Mellon Best, Dmitriy. > On Sep 22, 2015, at 10:10 AM, Chris Irwin <chris.ir...@sadasystems.com> wrote: > > I have CAS 4.0 connected to AD. This is working fine but I have one > application that would like me to return a different value for the user. > Today they log in with the sAMAccount name and this is returned as CAS:user > I also return the employeeID as part of the claim. It appears that their app > can’t extract the employeeID attribute from the claim and they want me to > insert employeeID in the place of the sAMAccount name. Can this be done? > > Sincerely, > > Christopher Irwin > > -- > You are currently subscribed to cas-user@lists.jasig.org > <mailto:cas-user@lists.jasig.org> as: dkopyle...@unicon.net > <mailto:dkopyle...@unicon.net> > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > <http://www.ja-sig.org/wiki/display/JSG/cas-user> -- You are currently subscribed to cas-user@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
