what is the reason for "Rest B" not being able to call "Rest A" like on you "internally" internal network without nay auth? OR having some "Rest C" as some front/facade User talks to, and then the Rest C talks to A and B as required?
regards, martin On Thursday, May 4, 2017 at 9:40:57 PM UTC+10, Erik wrote: > > > All, > > I'm looking at a CAS implementation where I have 2 REST services that are > CAS protected, but one of the services also calls the other service. It's > not clear from the CAS documentation what is the appropriate pattern in > that case. > > Access patterns: > > User -> Rest A (user calls Rest A directly) > > User -> Rest B -> Rest A (user calls Rest B, when then calls Rest A) > > Does each Rest Service get its own ticket or would you treat the Rest > services as a group and do a single service ticket for both of them? > > Thanks for the help. > > Erik > -- - CAS gitter chatroom: https://gitter.im/apereo/cas - CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html - CAS documentation website: https://apereo.github.io/cas - CAS project website: https://github.com/apereo/cas --- 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/1383787b-d3b3-4643-98b8-14ef41cc3cb6%40apereo.org.
