APIs are handled differently from SPAs. You probably need to look at the CAS REST protocol? https://apereo.github.io/cas/6.6.x/protocol/REST-Protocol.html
I would put APIs behind an API gateway. Conceptually they are the same thing as CAS + AD, but specifically designed for API calls, especially from background processes. On Fri, 2023-03-24 at 16:13 -0700, Pablo Vidaurri wrote: So how did you handle this. I too have API's behind CAS ... which is causing problems of its own. On Tuesday, November 22, 2022 at 10:56:47 PM UTC-6 Michael Remijan wrote: Hello user community, I am looking for some information on a CAS client and I haven’t been able to find it anywhere online. All CAS Client references I’ve find have been for configuring a Web App so that user login integrates with CAS for authentication. Unfortunately, this is not what I need. I have an REST API endpoint I need to integrate with in a headless/background process kind of way. Basic data integration stuff…periodically call the API throughout the day, get the data, process data. So I need an example of this kind of integration…having a background process pass the CAS authentication server what it needs to authenticate the request in a non-interactive, headless manner so my process can integrate with a REST API. Any examples like this exist? Any help would be appreciated. Mike -- - 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 cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/6bcdae894552b9763e2f1cbd1f0375f01abf5d4b.camel%40ndsu.edu.
