Thank you for your reply, Ray. System1 would serve as the main authentication server. Server 2 would authenticate against CAS and CAS would delegate this authentication to System1.
It's a bit confusing for me as well ;) I don't even know if what I'm thinking is possible... On Wednesday, December 20, 2017 at 1:21:13 PM UTC-5, rbon wrote: > > Jérémie, > > Are you saying that System 1 would perform the authentication to CAS on > behalf of the user or that System 1 can connect to System 2 as the user? > > CAS has a REST interface > https://apereo.github.io/cas/5.2.x/protocol/REST-Protocol.html > > Can System 1 be CASified? > > Ray > > On Wed, 2017-12-20 at 09:51 -0800, Jérémie Bourdon wrote: > > Hello, > > We are using 2 online systems that authenticate our users. > > System1 : local user authentication, allows other softwares to SSO in > through secret key, token and redirect URL > System 2 : local user authentication, allows authentication against CAS > server. > > My idea would be to integrate a CAS in between System1 < CAS server < > System2 so users can access System2 from System1 without re-authenticating. > > I'd like to know if this is possible. I can give more details about the 2 > systems if needed. > > Thank you very much for your help. > > Jérémie > > -- > Ray Bon > Programmer analyst > Development Services, University Systems > 2507218831 | CLE 019 | [email protected] <javascript:> > > -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/76ff2872-52be-455c-a0fa-235d999defc8%40apereo.org.
