This issue is actually resolved. We had some configurations and JS issues on our end that turned out to be the issues here.
That being said, the CORS filter settings on the CAS server are working as intended as of version 5.1.x. On Tuesday, August 22, 2017 at 2:56:24 PM UTC-4, Michael Matovic wrote: > > I've been working on some additional items that we deploy with our CAS > server, one of which happens to be a restful api that works alongside CAS. > I'm having issues now with OPTIONS requests not getting processed at all. I > understand that in CAS 5.1 (the version we are migrating to) there is a > CORS security filter but even when enabling this and instructing it to > accept all domains in its headers I'm still unable to complete a CORS > request successfully. Is there anything else that might be intercepting > these requests? > -- - 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/b76abba0-1e91-43e1-9283-c38db28e9030%40apereo.org.
