Hi Jérôme, Thanks for the quick reply! We already have the CAS OAuth 2.0 server in an evaluation environment, and I was trying to get a feel for how much modification would be needed to suit our needs to support a two-legged workflow with impersonation. We have been looking at Google's Service to Service OAuth 2.0 workflow with impersonation as a model for our needs:,
https://developers.google.com/accounts/docs/OAuth2ServiceAccount Obviously, there are other variants, but maybe it might be useful as one of many example implementations. Thank you, Edwin On Wed, Apr 3, 2013 at 10:49 PM, jleleu <lel...@gmail.com> wrote: > Hi, > > It would have been a good question for the CAS user mailing list. > > You can configure CAS to behave as an OAuth server following this > documentation : https://wiki.jasig.org/display/CASUM/OAuth+server+support. > > It's somehow limited and I have received a lot of requests for improvment > (especially these last days). > > Good timing : I'm planning a big refactoring for CAS 4.0. > > So far, there is no impersonation but it will be added : > https://issues.jasig.org/browse/CAS-1287. > > About the confirmation screen, you can't disable it, it will be displayed > for every service. Though, it can be some option to be defined by CAS > service (as a CAS service represents an OAuth application client). Just > added to CAS-1287. > > Hope we'll be able to do all of that for CAS 4.0. > > Best regards, > Jérôme > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > ed...@iplantcollaborative.org > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > -- You are currently subscribed to cas-dev@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-dev
