CAS can be used by anyone inside or outside VCU. Domains outside *.vcu.edu will require permission be granted to access CAS.
We have the CAS module pre-installed on dyn.vcu.edu.
There are several ways to use CAS with .NET. One option is the JA-SIG .Net CAS client, which is the JA-SIG officially supported method. This is also the method that we recommend at VCU.
You'll need to use the following configuration parameters to make it
work with VCU's CAS server:
<configuration> <appSettings> <add key="casLoginURL" value="https://login.vcu.edu/cas/login" /> <add key="casValidateURL" value="https://login.vcu.edu/cas/serviceValidate" /> <add key="serviceURL" value="URL to the main page of your application" /> </appSettings> ... </configuration>
There is a method that supports .net forms based authentication.
And a method with a pluggable IIS module.
It's up to you to choose your preferred method, based on the
requirements for your application.
When using a CAS client that does not directly support attributes (PHP, ASP.NET, etc.), the CAS XML response can be parsed to obtain the attribute information. The attributes are returned in the portion of the XML response, and each attribute is identified by where ZZZZ is the LDAP name of the attribute on the response.
<cas:serviceResponse xmlns:cas="http://www.yale.edu/tp/cas" xmlns:vcu="http://login.vcu.edu/cas"> <cas:authenticationSuccess> <cas:user>joeuser</cas:user> <vcu:attributes> <vcu:uid> joeuser </vcu:uid> <vcu:sn>User</vcu:sn> <vcu:givenName>Joe</vcu:givenName> <vcu:displayName>Mr. Joe User</vcu:displayName> </vcu:attributes> </cas:authenticationSuccess> </cas:serviceResponse>
This article was updated: 12/6/2017