CAS as Remote Authentication Handler in V3

[Michael Dahlberg]

Marvin, Andrew, and Leonard:

Thank you very much!  I appreciate your input.  Also, thank you immensely
for the link to Unicon's plugin.  I was not aware of that at all.

Mike

On Wed, Feb 10, 2016 at 4:31 PM, Leonard J. Peirce <
leonard.peirce+shibboleth at wmich.edu> wrote:

> On 16-02-10 03:07 PM, Michael Dahlberg wrote:
>
>> We're upgrading our Shib V2 installation to V3 (not actually doing the
>> upgrade, more like a migration).  Our current Remote
>> Authentication handler is an external CAS server setup according to the
>> directions at
>> https://wiki.jasig.org/display/CASUM/Shibboleth-CAS+Integration.
>> This documentation discusses using an external CAS server with IdPv2.
>> Can these same instructions be used to setup the V3 IdP to
>> use an external CAS server as a remote authentication handler?
>>
>>
>> The documentation in the wiki talks about using the internal CAS protocol
>> support with a server-side StorageService implementation.
>> I believe this is using the IdP as the CAS server.  We'd prefer to keep
>> our existing standalone CAS server.  Given that, is the
>> optimal method of seting up CAS Remote Authentication using the jar
>> libraries from JASIG?
>>
>
> I'm pretty much in the same boat with a V2 IdP using an external CAS
> server and migrating to  a new installation of a V3 IdP that must
> (at least in the short term) continue to use an external CAS server.
> I'm using the plugin here:
>
>    https://github.com/unicon/shib-cas-authn3
>
> In our test V3 IdP it is working nicely.
>
> - Leonard
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160211/87fa7f17/attachment-0001.html>