Hello,
I did some further examination and found out that setting
cas.authn.oidc.core.issuer to "https://cas.example.org:8443/cas/oidc; works
as well, but when replacing "cas.example.org" by anything else, the
discovery endpoint is broken.
Marcel
On Wednesday, June 7, 2023 at 6:05:06 PM UTC+2
Jérémie,
What do the cas logs say about the authentication event (may need debug level)?
The authorize URL comes after the authentication step. Are you logged in, in
that browser?
Ray
On Tue, 2023-06-27 at 06:30 -0700, Jérémie wrote:
Notice: This message was sent from outside the University
Jerome,
Sorry, I should have also mentioned that you need to enable the JSON service
registry (first link in my previous email). With your current config it is
using the in memory service registry.
And remember to put your service file in the destination directory.
Ray
On Tue, 2023-07-04 at
Baron,
There may be something in the fawnoos blog https://fawnoos.com/blog/
Ray
On Mon, 2023-07-03 at 15:48 -1000, Baron Fujimoto wrote:
Notice: This message was sent from outside the University of Victoria email
system. Please be cautious with links and sensitive information.
When using
Thank you that was helpful, my app was using the wrong trustore
On Sunday, July 2, 2023 at 12:46:27 PM UTC+1 p.bo...@centrum.cz wrote:
> Hi, provided you've got setup CAS and its certificate correctly, did you
> check that your Java client application really uses the truststore file
> located
Hello Ray
thanks for your answer so , I added :
cas.service-registry.json.location=file:/etc/cas/services
move cas.properties in /etc/cas/config
00:06:00 INFO [o.a.c.c.DefaultCasConfigurationPropertiesSourceLocator] -
2023-07-04 07:06:00,785 INFO
