Yan,
I was browsing the docs and
cas.authn.pac4j.saml[0].serviceProviderMetadataPath
cas.authn.pac4j.saml[0].serviceProviderEntityId
are for cas as a service provider metadata, not the destination application.
https://apereo.github.io/cas/6.6.x/integration/Delegate-Authentication-SAML.html
Ray
i think i am missing something fundamentally, but I do not know what it is.
I first excluded the dependency on cas-server-support-saml-idp because CAS
is delegating authN to Okta, I realize the login page does not even come
up, nothing shows in SAML Tracer. Then, I added this dependency, see
Yan,
Is it possible that the okta-cas config is incorrect and okta is returning an
error response which cas does not understand?
Are you using SAML Tracer to see the exchanges between SPs and IdPs?
If the keystore is not created, you can create it yourself. Or, turn off SAML
encryption between
Thanks for you answer, I found the solution myself.
No, the documentation is wrong and not updated.
The right thing to use is : servlet.servlet.context-path=/
It’s all in :
Julien,
This sounds like a tomcat config issue (I have not used embedded tomcat). Maybe
a config on this page
https://apereo.github.io/cas/6.6.x/installation/Configuring-Servlet-Container-Embedded-Tomcat.html
Ray
On Fri, 2023-08-11 at 08:53 -0700, Julien Weillaert wrote:
Notice: This message
Sanjay,
Version 5.1 is very old. It is difficult to know if this is a bug in that
version of cas or if it is a browser problem.
Your best, and safest, option is to upgrade and see if the issue persists.
Ray
On Thu, 2023-08-10 at 15:48 -0700, Sanjay Semwal wrote:
Notice: This message was sent
