Adam,
What are the errors/log messages (client and CAS and access)?
Perhaps it is a network issue. CAS must be able to connect to the callback.
Ray
On Thu, 2017-11-30 at 12:06 -0500, Adam Causey wrote:
We are using proxying with CAS 3 in one of our client applications and are
upgrading to CAS 5. However the client properties below do not seem to be
working with CAS 5.
What changes need to be made to support CAS 5 with this client?
<Parameter name="proxyCallbackUrl" value="https://
cas.example.com<http://cas.example.com>
/proxyCallback"/
>
<Parameter name="proxyReceptorUrl" value="/proxyCallback"/>
Thanks!
Adam
--
Ray Bon
Programmer analyst
Development Services, University Systems
2507218831 | CLE 019 | [email protected]
--
- 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/1512065971.1768.280.camel%40uvic.ca.
