Hi Bryan,

I don't see why the gateway feature would be required for the use case you 
describe.  If Canvas is to allow both CAS and a local-to-Canvas-account login, 
I'd have expected this to be accomplished by customizing the *Canvas* 
not-yet-authenticated experience to offer links for both CAS and 
local-to-Canvas login.

Cf. e.g. Yale's Sakai, which supports both CAS and local-to-Sakai login:

https://classesv2.yale.edu/portal/

Note the Yale CAS Login and the Non-Yale Login links at upper right.  No 
gateway feature usage required.

Gateway comes into the picture if, beyond supporting both CAS and non-CAS 
login, Canvas is looking to detect an already established CAS single sign-on 
session and skip presenting the invitation to login, jumping straight to the 
logged in experience when possible thanks to an already-established CAS single 
sign-on session.  I'd suggest that's possibly a better experience worth getting 
to, but not a nuance to address before eating basic CAS and non-CAS login 
working.

There's no issue with the gateway feature in the Yale CAS client that I know 
of.  That client library works just fine until/unless you need features it 
doesn't support.

Hope the conference call goes well.

Kind regards,

Andrew



On Jan 25, 2012, at 11:36 AM, Bryan E. Wooten wrote:

> Hi all,
>  
> We have deployed Canvas as our LMS and it is CASified. They have a 
> requirement allow both CAS and a “guest” login.
>  
> I have been asked to put a link on the CAS login page to the Canvas guest 
> login page. Through the magic of JSF / Javascript this link would only appear 
> if the service parameter points to the Canvas URL.
>  
> I don’t really like this idea and suggested they use the gateway feature that 
> grants access to some kind of Canvas landing page with the option to login 
> via CAS or their guest login. We have other apps that do this and it works 
> quite well.
>  
> Anyway they are having trouble making gateway work. I am not sure of the 
> exact issue. But I did see an exception when I went to their test server and 
> noted that they are using the Yale client. I realized this is no longer 
> supported. Also Canvas seems to be written in Grails.
>  
> So my question is this: Are there any known issues with the gateway feature 
> and the Yale client and / or frameworks like Grails? We have a conference 
> call set for later today with the Canvas developers.
>  
> Thanks for any help or advice,
> Bryan
> -- 
> You are currently subscribed to [email protected] as: [email protected]
> To unsubscribe, change settings or access archives, see 
> http://www.ja-sig.org/wiki/display/JSG/cas-user


-- 
You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-user

Reply via email to