I am looking into protecting an external standalone java application using CAS along with some other web based applications.
This standalone application ideally needs to authenticate through a library, but obviously will not have cookie access. Particularly if the standalone application authenticates after the web based applications register an authentication how does it acquire the correct CAS context? Alternatively in the case that if it is the first authenticator does anything special need to occur to create a cookie that can be seen by the other protected web applications, or will the cas server take care of this? We intend to use a single user context across all applications, once authentication has been successful. Finally is the best approach for this REST API or CAS Proxy authentication or is there a recommended approach? Many Thanks, Dan -- - 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/946b6c14-203b-472d-80c9-d8b175d60314%40apereo.org.
