...
| Tip | ||
|---|---|---|
| ||
These instructions are for CAS 2. For CAS 3, read the new article. |
A new version of Sakai brought many changes, one of which was how to CASify it.
...
In general it is recommended when using CAS to make it clear to the user when following a link will invoke CAS authentication. So we'll change the "Login" link to be "Login through CAS":
| Code Block | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
<input type="button" class="button" value="Login through CAS" onclick="parent.location='$login_url'" /> |
Also, optionally, we can add a link to Login without using CAS:
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<input type="button" class="button" value="Login without CAS" onclick="parent.location='/login'" /> |
...
This invokes the Sakai internal login dialog, without invoking our single
sign-on system.
- Glenn
...
On Nov 12, 2004, at 6:11 AM, Vishal Goenka wrote:
...
The one thing I haven't found a way to resolve, is to ensure that CAS is triggered only for the authenticated portion of Sakai. Since the non-authenticated access to Site Info etc. isn't distinguished based on URL, rather is based on session context, I have to enable the CAS Filter for <url-pattern>/*</url-pattern>.
Thanks.
- Vishal
Vishal Goenka
SunGard SCT
Advisory Technical Architect, Luminis Solutions
+91 80 511 42767 (Office)
+91 98455 46487 (Mobile)
Time Zone: GMT +5:30
vgoenka@sungardsct.com
www.sungardsct.com
...