mmoayyed on master
add test for config profiles an… (compare)
mmoayyed on heroku-githubbot
update notes (compare)
hey people... thats not true... is anything working on this project or is everything fake?? realy, thats not nice:
Starting a Gradle Daemon, 3 incompatible and 1 stopped Daemons could not be reused, use --status for details
Task :bootWar FAILED
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':bootWar'.
Error while evaluating property 'mainClass' of task ':bootWar'
Failed to calculate the value of task ':bootWar' property 'mainClass'.
Main class name has not been configured and it could not be resolved
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
Get more help at https://help.gradle.org
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
BUILD FAILED in 2m 23s
9 actionable tasks: 9 executed
I'm still trying to use the functionality of cas-management 6.3.x
At the moment version 6.3.4 has errors in the "attribute release" and "access strategy" tabs. Version 6.3.5-SNAPSHOT, fixes this, but overrides the troubleshooting in the "properties" tab, Fixed error with authn policies tab # 194
Someone could help me solve or contribute to the solution of this.
Hi, we are using CAS 6.4.0 with GoogleAuthenticator Multi-Factor enabled, but every time we reboot CAS the tokens provided by the GoogleAuthenticator App for the users stops working.
This seems to be related to the secret for the specific couple user/device that CAS is not able to recover after reboot (the internal service endpoint '
gauthCredentialRepository' doesn't return it in response to a GET
To reproduce this issue:
We think this is a bug, but any help to resolve this critical issue will be appreciated.
Hi guys, I am setting up the CAS version 6.3.6 via K8s . I just prepare the image in the Container Registry. The gradle.build is remain the same as I don't add any new dependencies. But I don't know why it keeps saying this error.
"WARN [org.apereo.cas.web.CasWebApplicationContext] - <Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanDefinitionStoreException: Failed to process import candidates for configuration class [org.apereo.cas.web.CasWebApplication]; nested exception is java.lang.IllegalStateException: Error processing condition on org.springframework.boot.actuate.autoconfigure.quartz.QuartzEndpointAutoConfiguration>"
Hope someone helps me! Much appreciated
Hello, I am using jasig 6.3 and I am trying customize it with the overlay. I m trying to override some bean with Java code but the gradle build is unable to compile due to missing symbols, even the most core symbols are missing in the compilation process (i.e.
UsernamePasswordCredential from cas-server-core-authentication.
Is there something to tune in build.gradle to allow override java beans?
2021-10-12 18:06:47,586 ERROR [org.apereo.cas.support.saml.web.idp.profile.AbstractSamlIdPProfileHandlerController] - <NullPointerException> java.lang.NullPointerException: null at java.util.HashMap.putMapEntries(Unknown Source) ~[?:?] at java.util.HashMap.putAll(Unknown Source) ~[?:?]
Hi, I'm using the CAS (6.3.5) OIDC module and a REST authentication backend. It's working fine, but now I'd like to provide a better error explanation when using the "password grant" workflow. The REST backend is returning different 4xx codes according to the specific situation (invalid credentials, expired password, etc). However, this information is lost somewhere inside the authentication request, resulting in just a generic 401 error code.
Is there a way to customize the "unauthorized" message so it includes a message (or message key) related to the actual exception thrown by the backend provider ?