Sorry, more questions:
I also tried setting the property *cas.authnofor throttle.failure.code* to
"AUTHENTICATION_FAILED_THROTTLED" in an attempt to make the cause for this
failure mode more apparent.
However, the string never shows up in the logs. I don't see any differences if I leave it
at
In our case, we run five servers (cas-srv01, cas-srv02, etc.) behind an F5
load balancer. The VIP on the F5 identifies as "sso.newschool.edu". We use
one "regular" SSL/TLS certificate for "sso.newschool.edu" and install it
both on the F5 AND on each of the CAS servers (in the Tomcat keystore) so
th
Mahalo, Jérôme!
On Thu, Sep 10, 2020 at 07:56:54AM +0200, Jérôme LELEU wrote:
Hi,
The value of the *cas.authn.throttle.usernameParameter* property must be
the name of the request parameter holding the username (from the login
form), which is "username".
Thanks.
Best regards,
Jérôme
Le mer. 9
Hello all,
Please does anyone have familiarity with the SAML certificate and metadata
generation process? Specifically how to create them for a HA deployment
where users will sign in to server.onu.edu and authentication will be
performed on either server-1.onu.edu or server-2.onu.edu?
On Wedne
This was an obvious mistake; sorry about that. The repo status is restored.
On Thu, Sep 10, 2020 at 6:31 PM randomuser878 wrote:
>
> Greetings
>
> Can not add anything concrete to your observation.
> This looks promising
> https://apereo.github.io/cas/development/release_notes/RC2.html#d
Hi,
Yes, it cannot work in the old versions of CAS.
An intermediate component has been added in more recent versions to handle
that.
I recommend upgrading to v6.1 or v6.2.
Thanks.
Best regards,
Jérôme
Le jeu. 10 sept. 2020 à 15:55, Peter Lee a écrit :
> I don't get the http request in the brow
Greetings
Can not add anything concrete to your observation.
This looks promising
https://apereo.github.io/cas/development/release_notes/RC2.html#dynamic-jpa-service-management
in terms of future of the component but totally unclear how does it fit
with your observation of archived rep
I don't get the http request in the browser. The link at the login page
button is extracted from pac4jUrls object for redirect (looks like it's for
redirect binding, this button works when destinationbinding is set to
redirect).
So it seems what I am missing is to get the POST body and set it to
Hi,
Regarding the logs, it seems to be working.
Do you see the SAML authn request posted in your browser logs?
Thanks.
Best regards,
Jérôme
Le jeu. 10 sept. 2020 à 14:28, Peter Lee a écrit :
> I am using v5.2.9. I've set the
> *cas.authn.pac4j.saml[0].destinationbinding=urn:oasis:names:tc:SAML
I am using v5.2.9. I've set the
*cas.authn.pac4j.saml[0].destinationbinding=urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST.*
I do see POST body is being created according to the log, is POST binding
not fully supported yet in this version?
Or am I missing jar files in build to associate Velocit
10 matches
Mail list logo
