[cas-user] cas-management support for CAS v6.4+?

Dear CAS maintainers/developers, are there any plans for cas-management application to support CAS v6.4+? Thank you, in advance, Pavlos -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://go

Re: [cas-user] CAS 6.3.x problem with style?

Hi Bartek, We had the same issue and it seems that it was caused by jsessionid that it was appended in the URL... Adding in web.xml (in ),COOKIE, solved the problem for us. Best Regards, Pavlos On Thu, Apr 1, 2021 at 12:32 PM Bartosz Nitkiewicz wrote: > Hi, > We have a problem with proper loa

Re: [cas-user] CAS 6.3.2 Google Auth OTP Validation Issue

Hi Philippe, it seems that gauth validation, is now fixed ( https://github.com/apereo/cas/commit/e7cb3b8b44867addcb6b8510cbbed45cbc9b265f ). Pavlos On Tue, Mar 9, 2021 at 10:19 PM 'Philippe MARASSE' via CAS Community < cas-user@apereo.org> wrote: > Folks, > > Since we've installed our new cas v

Re: [cas-user] 6.2.x Gradle Compilation

By default, systemd, allows tomcat to write only under the following directories: /etc/tomcat9/Catalina/ /var/lib/tomcat9/webapps/ /var/log/tomcat9/ So, you should override systemd - tomcat settings, to allow writing to any other directory (/var/log/ in your case). Add the following in /etc/syste

[cas-user] discoveryProfile xml parse error

Hi all, when accessing the dicoveryProfile end point via browser, I get the following error message: XML Parsing Error: not well-formed Location: https://cas.example.com/actuator/discoveryProfile Line Number 1, Column 50: org.apereo.cas.services.Rege

[cas-user] CAS 6.x NPE during ticket validation, when using adaptive mfa.

Hi all, it seems that in CAS 6.x (tested against latest 6.0.x and 6.1.0-RC4 tree), adaptive mfa flow is triggered also during the ticket validation process. As a consequence, when checking if agent matches the allowed pattern, ticket validation fails with the following NPE, as agent is null 2019-

Re: [cas-user] CAS 5.1.5 Login View Title

Hi Mac, I think that you have to change the title element in classes/templates/layout.html... Cheers, Pavlos On 13/12/2017 06:43 μμ, Mac Reid wrote: Hi all, I am trying to modify the HTML title of the default theme. I have added a custom messages file (src/main/resources/custom_messages

Re: [cas-user] Re: Release Attributes from LDAP Authentication

Hi, have you enabled sso server to release attributes to your service (https://apereo.github.io/cas/5.1.x/integration/Attribute-Release-Policies.html) ? Pavlos On 30/06/2017 03:27 μμ, Rafa wrote: Hi, I'm using CAS protocol and validating ST against the /p3/serviceValidate. I'm not familiar

Re: [cas-user] Re: CAS 5.1 Risk Based Authentication issues

Hi Ludovic, I think that the purpose of this property is for "registering" risk-based authentication in authentication handlers and that its value is just a name, could be whatever. If none is specified, the default triggeredRiskBasedAuthentication, will be used. Pavlos On 26/06/2017 05:48

Re: [cas-user] Re: CAS 5.1 Risk Based Authentication issues

Hi, I just did a PR for this issue (https://github.com/apereo/cas/pull/2721), but there is no review yet. Pavlos On 26/06/2017 04:05 μμ, Ludovic Senecaux wrote: I had an issue when I try to login... Have you got an idea ? | WHO:foo WHAT:org.hibernate.QueryException:could notresolve propert

Re: [cas-user] Re: CAS 5.1 Risk Based Authentication issues

Hi Ludovic, yes, I finally understood what was wrong, see here: https://github.com/apereo/cas/pull/2716 To disable google-maps-library dependency, add an exclusion to your pom.xml like this: org.apereo.cas cas-server-support-electrofence ${cas.version}

Re: [cas-user] CAS 5.1 Password expired issues

Hello all, just for future reference... PPolicy issues are now fixed in v5.1.1. There is no need to add anything in the login-webflow.xml... Pavlos On 22/06/2017 08:31 μμ, Pavlos Drandakis wrote: Hi Ben, No, I hadn't, but I just did it: https://github.com/apereo/cas/issues/2703 C

Re: [cas-user] CAS 5.1 Password expired issues

ed it as a bug or anything already? It looks like the above states are being set up by DefaultWebflowConfigurer.createHandleAuthenticationFailureAction() but they aren't having any effect. (Also, thanks for the workaround :) On 17 June 2017 at 17:14, Pavlos Drandakis <mailto:pdra...@noc

Re: [cas-user] CAS 5.1 Password expired issues

Yes, you are right, I 've only checked messages.properties... I have no thymeleaf experience and surely someone else could help you more. Nevertheless I 've found that, perhaps, the following, is what you are looking for: "#{screen.mustchangepass.message(${@environment.getProperty('cas.authn.p

Re: [cas-user] CAS 5.1 Password expired issues

it is explained here : http://www.thymeleaf.org/doc/tutorials/2.1/usingthymeleaf.html#variables Regards, Le 21 juin 2017 16:25, "Pavlos Drandakis" <mailto:pdra...@noc.edunet.gr>> a écrit : On 21/06/2017 12:10 μμ, Ludovic Senecaux wrote: Thanks Pavlos, it works !

Re: [cas-user] CAS 5.1 Password expired issues

On 21/06/2017 12:10 μμ, Ludovic Senecaux wrote: Thanks Pavlos, it works ! Glad to hear it :-) Have you found any workarouds for : 1/ the use of pwdGraceAuthNLimit When pwdGraceAuthNLimit was enabled, I was keep getting NPE in logs and nothing in login form. After this change: https://githu

Re: [cas-user] CAS 5.1 Password expired issues

Hi Ludovic, it seems that adding the following in login-webflow.xml, solves the problem: Cheers, Pavlos On 20/06/2017 10:37 πμ, Ludovic Senecaux wrote: It works when I add "pwdAccountLockedTime" attribute for a user. But when I add "pwdReset = TRUE", I got 2 | 017-06-2008:56:34,445ERROR [o

[cas-user] CAS 5.1 Risk Based Authentication issues

Hello all, I am trying to enable Risk Based Authentication in CAS 5.1.0. by following the documentation (https://apereo.github.io/cas/5.1.x/installation/Configuring-RiskBased-Authentication.html). I have added cas-server-support-electrofence in pom.xml, I have enabled tracking and recording authen

Re: [cas-user] CAS 5.1 Password expired issues

Eventually, everything seems to work ok, after adding in login-webflow.xml the following (which is present in CAS v5.0.x but not in CAS v5.1.0): expression="authenticationExceptionHandler.handle(currentEvent.attributes.error, messageContext)"/> to="casAccountDisabledView"/

Re: [cas-user] CAS 5.1 Password expired issues

configuration for CAS 5.1.0 - OpenLDAP - LPPE support? Thanks, in advance, Pavlos > This bug https://github.com/apereo/cas/issues/2322 previously could stop > the expired password being handled but it's fixed in 5.1 RC2. > > On 8 June 2017 at 15:10, Pavlos Drandakis w

Re: [cas-user] CAS 5.1 Password expired issues

tions, including CredentialExpiredException. > > > On 7 June 2017 at 13:54, Pavlos Drandakis wrote: > >> Hello all, >> >> I am trying to setup CAS 5.1 (using the maven overlay method) to >> authenticate users against an OpenLDAP server. If user's password is not

Re: [cas-user] CAS 5.1 Password expired issues

the different exceptions, including CredentialExpiredException. On 7 June 2017 at 13:54, Pavlos Drandakis <mailto:pdra...@noc.edunet.gr>> wrote: Hello all, I am trying to setup CAS 5.1 (using the maven overlay method) to authenticate users against an OpenLDAP ser

[cas-user] CAS 5.1 Password expired issues

Hello all, I am trying to setup CAS 5.1 (using the maven overlay method) to authenticate users against an OpenLDAP server. If user's password is not expired, everything works as expected. But, when user's password expires, all I get is the "Invalid credentials" error in login page instead of the p