mmoayyed on master
support ldap throttling support expiration window for l… upgrade dependencies (compare)
mmoayyed on 6.5.x
Handle multi use token for rese… (compare)
mmoayyed on master
fix build failures fix tests (compare)
mmoayyed on master
Handle multi use token for rese… (compare)
Hey! Nobody noticed that the last version of CAS client for Java, its build for Java 8, but have a dependency to JAXB 2.3.1 that its for Java 9 ?
Also, the READMED should clarify what version of Java it's being supported.
Anyone could annotate this on the issues system that you are using ? I would liked to do this, but I don't see that I could done on GitHub repo, and I don't see a Jira o r Mantis to do it.
attributeReleasePolicy: !<org.apereo.cas.services.ReturnMappedAttributeReleasePolicy>
allowedAttributes: !<java.util.TreeMap>
mail: !<java.util.ArrayList>
- "mail"
principalAttributesRepository: !<org.apereo.cas.authentication.principal.DefaultPrincipalAttributesRepository>
attributeRepositoryIds: !<java.util.HashSet>
- "*"
consentPolicy: !<org.apereo.cas.services.consent.DefaultRegisteredServiceConsentPolicy>
status: "FALSE"
excludeDefaultAttributes: true
authorizedToReleaseAuthenticationAttributes: false
For 6.4x -> 6.5-SNAPSHOT we're trying to identify the following issue:
2022-02-03 12:19:54,805 -0700 WARN [io.netty.bootstrap.Bootstrap] - <Failed to set channel option 'CONNECT_TIMEOUT_MILLIS' with value '5000' for channel '[id: 0xf39d1e89]'>
This appears to break LDAP connection for the service registry.
We've also seen a few parameters change formatting in docs, but don't necessarily error/warn in the container, so it seems confusing to debug at the moment.
Caused by: com.fasterxml.jackson.databind.exc.MismatchedInputException: Cannot deserialize value of typejava.lang.String
from Array value (tokenJsonToken.START_ARRAY
)
at [Source: UNKNOWN; line: -1, column: -1] (through reference chain: org.apereo.cas.support.oauth.services.OAuthRegisteredService["supportedGrantTypes"]->java.util.HashSet[1])
hello i am using /cas/v1/tickets rest api when integating qr login, but when i curl this api like this: “curl -X POST -k -d 'username=user1@test.com&password=testpass&token=true&additionalParam1=paramvalue' "https://localhost:8442/cas/v1/tickets”
I got this error:
"Service is not found in service registry."
solved, appending a service param can solve this.
cas.authn.authentication-attribute-release.enabled=false
I want to define a register using overlay, I put a controller directly into the src/main/java directory
@RestController
public class RegisterController {
@RequestMapping("/register")
public String register(String userName,String password) {
return "register success " + userName;
}
}
2022-02-18 10:35:33,281 ERROR [org.apache.catalina.core.ContainerBase.[Tomcat].[localhost].[/cas].[dispatcherServlet]] - <Servlet.service() for servlet [dispatcherServlet] in context with path [/cas] threw exception [Request processing failed; nested exception is java.lang.IllegalStateException: Cannot call sendRedirect() after the response has been committed] with root cause>
java.lang.IllegalStateException: Cannot call sendRedirect() after the response has been committed
at org.apache.catalina.connector.ResponseFacade.sendRedirect(ResponseFacade.java:488) ~[tomcat-embed-core-9.0.58.jar!/:9.0.58]
(...)
at org.apereo.cas.web.support.AuthenticationCredentialsThreadLocalBinderClearingFilter.doFilter(AuthenticationCredentialsThreadLocalBinderClearingFilter.java:28) ~[cas-server-core-web-api-6.5.0.jar!/:6.5.0]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) ~[tomcat-embed-core-9.0.58.jar!/:9.0.58]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) ~[tomcat-embed-core-9.0.58.jar!/:9.0.58]
at org.apereo.cas.web.support.filters.RequestParameterPolicyEnforcementFilter.doFilter(RequestParameterPolicyEnforcementFilter.java:401) ~[cas-server-core-web-api-6.5.0.jar!/:6.5.0]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) ~[tomcat-embed-core-9.0.58.jar!/:9.0.58]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) ~[tomcat-embed-core-9.0.58.jar!/:9.0.58]
at org.apereo.cas.web.support.filters.ResponseHeadersEnforcementFilter.doFilter(ResponseHeadersEnforcementFilter.java:200) ~[cas-server-core-web-api-6.5.0.jar!/:6.5.0]
(...)
Hello there,
We are trying to enable FIDO2 WebAuthN support in CAS with both Yubikeys and using the built-in browser support for FIDO2, namely for Safari on Mac OS.
While Yubikey registration and authentication works fine out of the box, when trying to register a FIDO2 device using the native Safari support for FIDO2 (without a Yubikey), we are presented with the following error on the registration step :
"java.lang.IllegalArgumentException: Failed to obtain attestation trust anchors."
Any ideas why this is happening and maybe how we can configure our own attestation trust anchors to include other sources than Yubikeys ?
cas.authn.mfa.web-authn.redis.host=172.24.200.126
cas.authn.mfa.web-authn.redis.port=6379
cas.authn.mfa.web-authn.redis.password=xxxxx
cas.authn.mfa.web-authn.redis.enabled=true
cas.authn.mfa.web-authn.redis.database=6
cas.authn.mfa.web-authn.core.enabled=true
cas.authn.mfa.web-authn.core.display-name-attribute=sAMAccountName
#cas.authn.mfa.web-authn.core.relying-party-name=CAS WebAuthn
cas.authn.mfa.web-authn.core.allow-primary-authentication=false
cas.authn.mfa.web-authn.core.allow-unrequested-extensions=false
cas.authn.mfa.web-authn.core.allow-untrusted-attestation=true
cas.authn.mfa.web-authn.core.validate-signature-counter=true
cas.authn.mfa.web-authn.core.trusted-device-enabled=false
#cas.authn.mfa.web-authn.core.relying-party-id=xxxx
cas.authn.mfa.web-authn.crypto.enabled=true
cas.authn.mfa.web-authn.crypto.signing.key=********
cas.authn.mfa.web-authn.crypto.encryption.key=***********
cas.authn.mfa.web-authn.redis.read-from=MASTER