| Tip |
|---|
| Purpose of this manual page |
|---|
| icon | false |
|---|
| Purpose of this manual page |
|---|
| icon | false |
|---|
|
This manual page is intended to be a quick guide for CASifying uPortal. It is current as of uPortal 3.x and tailored to 3.x. There are a number of ways to CASify a uPortal. You don't have to do it this way. This is, however, the standard way. |
...
CASifying uPortal requires the Java CAS Client. The necessary dependencies are included with uPortal. You should not need to change the Java CAS Client version, however, if you do,edit the main pom.xml as follows
| Code Block |
|---|
| xml |
|---|
| xml |
|---|
| title | Editing the Java CAS Client Version if neededxml |
|---|
|
<!-- Project Dependency Version Properties -->
<casclient.version>2.2.0-M2</casclient.version>
|
...
The filter is mapped over the /Login path because the CAS ticket is treated like other uPortal security credentials. You'd send your password to /Login if you were authenticating via password. You send your ticket to /Login to authenticate via CAS.
| Code Block |
|---|
| xml |
|---|
| xml |
|---|
| title | Declaring and mapping the necessary filtersxml |
|---|
|
<filter>
<filter-name>CAS Validate Filter</filter-name>
<filter-class>edu.yale.its.tp.cas.client.filter.CASValidateFilter</filter-class>
<init-param>
<param-name>edu.yale.its.tp.cas.client.filter.validateUrl</param-name>
<param-value>http://your.cas.server.com/cas/serviceValidate</param-value>
</init-param>
<init-param>
<param-name>edu.yale.its.tp.cas.client.filter.serverName</param-name>
<param-value>yourportal.server.com</param-value>
</init-param>
<init-param>
<param-name>edu.yale.its.tp.cas.client.filter.proxyCallbackUrl</param-name>
<param-value>http://yourportal.server.com/uPortal/CasProxyServlet</param-value>
</init-param>
</filter>
|
| Warning |
|---|
|
It is VERY important that you remove the following init-param for production | Code Block |
|---|
| xml |
|---|
| xml |
|---|
| title | Remove This!xml |
|---|
|
<init-param>
<param-name>BROKEN_SECURITY_ALLOW_NON_SSL</param-name>
<param-value>NOT_SECURE_DO_NOT_USE_THIS_SETTING_IN_PRODUCTION</param-value>
</init-param>
|
|
...