Thanks very much for the follow up. I just found that myself. Here are some
more details.
Related log entries:
2018-10-26 14:37:24,325 DEBUG [org.apereo.cas.config.CasCoreConfiguration]
-
2018-10-26 14:37:24,325 WARN
Now that I am in front of my computer, the property is this:
cas.authn.shibIdp.serverUrl=
On Fri, Oct 26, 2018 at 7:00 AM Travis Schmidt
wrote:
> We do the same as well, looks like docs might need to be updated. You
> should only need to add support-shibboleth to your build, but there is a
>
We do the same as well, looks like docs might need to be updated. You
should only need to add support-shibboleth to your build, but there is a
property that needs to be set that is your shibboleth idp url. You should
see something in the logs on start up about it not being set.
On Fri, Oct 26,
We have a Shibboleth 3.3.x server which will authenticates via our CAS
5.3.x server. I am interested in using the service provider's entity ID to
apply configuration within CAS rather than applying configuration to the
Shibboleth service as a whole. This appears to be possible based on:
is there any CAS client for Node js, if yes then please provide a link for
it and also share the details about how to use it?
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions:
Hi Baron,
Looking at the source code, you can see that *evaluationOrder *is only an
integer
https://github.com/apereo/cas/blob/v5.0.10/core/cas-server-core-services/src/main/java/org/apereo/cas/services/AbstractRegisteredService.java#L77
And for Java, integer have a limit to it (A quick google
