Hi Pranee,
The error you have is seems to be that the CAS Management cannot connect to
mdq.incommon.org:443. Have you checked if you have access to that address
from your local machine running CAS Mgmt? Can you telnet/ping that site?
If you are not able to open access, you can try to add the fol
Follow up, for anyone running into this situation. One of the problems was a
lack of understanding, and the other was a “maybe” configuration error.
Turns out the attribute definitions were working, but they do not show up in
availableAttributes as output by the cas/actuator/discoveryProfile en
Add server.port=8443 to the cas.properties file to over come this error.
Hopefully it will help someone some day as this is not mentioned in any
documentation anywhere.
On Friday, 28 January 2022 at 07:01:52 UTC-6 Adarsh wrote:
> Hi, I am trying to setup a CAS (6.5.0-SNAPSHOT) server with PAC4j
Good morning. We have a similar architecture, but slightly different. We run
an internal/ external view of DNS that routes one to either an on-prem load
balancer if they are on-prem or an off-prem load balancer if they are off-prem.
Behind each LB we run two CAS servers. All four CAS servers
Thank you Ray.
I have to test, because i want replace my shibboleth server with my jasig
server
Le vendredi 28 janvier 2022 à 19:03:22 UTC+1, Ray Bon a écrit :
> Vallee,
>
> You can define multiple attribute repositories,
> https://apereo.github.io/cas/6.4.x/integration/Attribute-Resoluti
