mmoayyed on 6.5.x
fix: attribute encoder fails wi… (compare)
mmoayyed on master
fix build support webauthn devices for ac… deprecate digest and fortress m… and 4 more (compare)
mmoayyed on 6.5.x
Fix null issuer for JWS/JWE on … (compare)
mmoayyed on master
use proper beans for attribute … minor formatting fixes fix issue with attribute encodi… (compare)
mmoayyed on 6.5.x
fix issue with attribute encodi… (compare)
mmoayyed on master
move registered service fields … allow saml2 sign responses to b… support rest-based policy for p… and 4 more (compare)
mmoayyed on master
Fix issuer null for JWS/JWE on … (compare)
error: release version 11 not supported
Hi, i'm trying to activate acceptable usage policy and get this Error: [..] in state 'acceptableUsagePolicyView' of flow 'login' -- action execution attributes were 'map[[empty]]' [..]
any ideas on how to fix this?
Usually this happens when the query to find the aupAccepted value doesn't return anything at all. For example if you are using JDBC with 'SELECT aupAccepted from user where username = ?' and there is no row for the username specified then you will get the error you are seeing
Anyone knows how to fix this error when creating an Oauth2 service on cas management?
2021-06-29 05:01:59,854 INFO [org.pac4j.core.profile.ProfileHelper] - <Building user profile based on typedId: [email]>
2021-06-29 05:02:33,169 INFO [org.apereo.inspektr.audit.support.Slf4jLoggingAuditTrailManager] - <Audit trail record BEGIN
=============================================================
WHO: [email]
WHAT: IO error opening file stream.
ACTION: SAVE_SERVICE_FAILED
APPLICATION: CAS_Management
WHEN: Tue Jun 29 05:02:33 WGST 2021
CLIENT IP ADDRESS: 192.168.0.98
SERVER IP ADDRESS: 192.168.0.73
=============================================================
>
2021-06-29 05:02:33,185 ERROR [org.apache.catalina.core.ContainerBase.[Tomcat].[localhost].[/cas-management].[dispatcherServlet]] - <Servlet.service() for servlet [dispatcherServlet] in context with path [/cas-management] threw exception [Request processing failed; nested exception is java.lang.IllegalArgumentException: IO error opening file stream.] with root cause>
java.io.IOException: The service definition file could not be saved at /etc/cas/services/ex-1624950153058.json
at org.apereo.cas.services.resource.AbstractResourceBasedServiceRegistry.save(AbstractResourceBasedServiceRegistry.java:184) ~[cas-server-core-services-registry-6.3.2.jar!/:6.3.2]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
at org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:282) ~[spring-core-5.2.12.RELEASE.jar!/:5.2.12.RELEASE]
at org.springframework.cloud.context.scope.GenericScope$LockedScopedProxyFactoryBean.invoke(GenericScope.java:499) ~[spring-cloud-context-2.2.6.RELEASE.jar!/:2.2.6.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) ~[spring-aop-5.2.12.RELEASE.jar!/:5.2.12.RELEASE]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212) ~[spring-aop-5.2.12.RELEASE.jar!/:5.2.12.RELEASE]
at com.sun.proxy.$Proxy119.save(Unknown Source) ~[?:?]
at org.apereo.cas.services.DefaultChainingServiceRegistry.lambda$save$0(DefaultChainingServiceRegistry.java:44) ~[cas-server-core-services-registry-6.3.2.jar!/:6.3.2]
at java.util.ArrayList.forEach(ArrayList.java:1541) ~[?:?]
at org.apereo.cas.services.DefaultChainingServiceRegistry.save(DefaultChainingServiceRegistry.java:44) ~[cas-server-core-services-registry-6.3.2.jar!/:6.3.2]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
[continues]
The program is being ran as root, so it should have access to the directory. Also this only happens for some services, for example open id works.
attributeReleasePolicy
to the service definition and listing the allowedAttributes. However, it would be nice to control which attributes are returned for which standard or custom scope. How can this be accomplished?
Hi, i'm trying to activate acceptable usage policy and get this Error: [..] in state 'acceptableUsagePolicyView' of flow 'login' -- action execution attributes were 'map[[empty]]' [..]
any ideas on how to fix this?Usually this happens when the query to find the aupAccepted value doesn't return anything at all. For example if you are using JDBC with 'SELECT aupAccepted from user where username = ?' and there is no row for the username specified then you will get the error you are seeing
Problem was a missing (and valid) cas.acceptable-usage-policy.aup-policy-terms-attribute-name=XXXXX config option. Wasn't aware that this is mandatory
Hi, i'm trying to activate acceptable usage policy and get this Error: [..] in state 'acceptableUsagePolicyView' of flow 'login' -- action execution attributes were 'map[[empty]]' [..]
any ideas on how to fix this?Usually this happens when the query to find the aupAccepted value doesn't return anything at all. For example if you are using JDBC with 'SELECT aupAccepted from user where username = ?' and there is no row for the username specified then you will get the error you are seeing
Problem was a missing (and valid) cas.acceptable-usage-policy.aup-policy-terms-attribute-name=XXXXX config option. Wasn't aware that this is mandatory
Glad you got it sorted! Having an invalid value would also lead to no row being returned which would throw the same error that I had come across before.
Hi, i'm trying to activate acceptable usage policy and get this Error: [..] in state 'acceptableUsagePolicyView' of flow 'login' -- action execution attributes were 'map[[empty]]' [..]
any ideas on how to fix this?Usually this happens when the query to find the aupAccepted value doesn't return anything at all. For example if you are using JDBC with 'SELECT aupAccepted from user where username = ?' and there is no row for the username specified then you will get the error you are seeing
Problem was a missing (and valid) cas.acceptable-usage-policy.aup-policy-terms-attribute-name=XXXXX config option. Wasn't aware that this is mandatory
Glad you got it sorted! Having an invalid value would also lead to no row being returned which would throw the same error that I had come across before.
CAS 6.3.2
Hi, i'm also trying to activate acceptable usage policy (with ldap storage) and the same error occur when my browser locale is set to fr (which matches messages_fr.properties file), no error when the browser locale is set to fr-FR
I don't understand what would be a valid cas.acceptable-usage-policy.aup-policy-terms-attribute-name=XXXXX config option, can someboby help me please ?
Hi, building the cas-configserver-overlay i got an error getting the resource https://dl.bintray.com/scalding/generic/waroverlay.gradle , because it looks like this URL is dead. Where can I find an alternative to build this project ? Any hints ?
I ran into the same problem. I solved it by changing my build.gradle
:
// on line 11 add the following dependency
classpath "org.scaldingspoon.gradle:gradle-waroverlay-plugin:0.9.3"
// replace the following line
apply from: "https://dl.bintray.com/scalding/generic/waroverlay.gradle"
// with this one
apply plugin: 'waroverlay'
{
"@class" : "org.apereo.cas.services.OidcRegisteredService",
"clientId": "registry",
"clientSecret": "XXX",
"serviceId" : "https://YYYYYYY/c/oidc/callback",
"name": "Example",
"id": 10,
"scopes" : [ "java.util.HashSet",
[ "openid","profile", "email"]
]
}
Hello 👋,
I am trying to add new attributes to the "/oidc/profile" EP.
we added new claims that linked to a new scope, and attribute fetch from rest api.
the call to fetch the attributes from the rest api works well on login.
unfortunately, when we call the profile we cannot see the new attributes.
the additional envs to configure it are:
cas.auth.oidc.user-defined-scopes.newScope= claims list
cas.auth.oidc.scopes=openid,profile,email,newScope
cas.auth.attribute-repository.rest= (with the full configuration)
we add new attributes that relevent for our system, but unfortunately we can see only name/id/email, and language for example is not added.
any idea why? or if I am missing something?
thank you in advance
Error build CAS 6.3.6
2021-08-09 20:27:24,588 INFO [org.apereo.cas.configuration.DefaultCasConfigurationPropertiesSourceLocator] - <Configuration files found at [/etc/cas/config] are [[file [/etc/cas/config/cas.properties]]] under profile(s) [[standalone]]>
2021-08-09 20:27:25,070 INFO [org.apereo.cas.web.CasWebApplication] - <The following profiles are active: standalone>
2021-08-09 20:27:26,953 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>
pls solution?
=============================================================
WHO: audit:unknown
WHAT: For input string: "auto"
ACTION: SAML2_RESPONSE_CREATED
APPLICATION: CAS
WHEN: Thu Aug 12 14:05:51 GMT 2021
CLIENT IP ADDRESS: windows_browser_client
>
2021-08-12 14:05:51,401 DEBUG [org.apereo.cas.web.FlowExecutionExceptionResolver] - <Ignoring the received exception [java.lang.NumberFormatException: For input string: "auto"] due to a type mismatch with handler [org.apereo.cas.support.saml.web.idp.profile.sso.SSOSamlIdPProfileCallbackHandlerController#handleCallbackProfileRequest(HttpServletResponse, HttpServletRequest)]>
2021-08-12 14:05:51,401 DEBUG [org.apereo.cas.web.FlowExecutionExceptionResolver] - <Ignoring the received exception [java.lang.NumberFormatException: For input string: "auto"] due to a type mismatch with handler [org.apereo.cas.support.saml.web.idp.profile.sso.SSOSamlIdPProfileCallbackHandlerController#handleCallbackProfileRequest(HttpServletResponse, HttpServletRequest)]>
2021-08-12 14:05:51,404 ERROR [org.apache.catalina.core.ContainerBase.[Tomcat].[localhost].[/casphp].[dispatcherServlet]] - <Servlet.service() for servlet [dispatcherServlet] in context with path [/casphp] threw exception [Request processing failed; nested exception is java.lang.NumberFormatException: For input string: "auto"] with root cause>
java.lang.NumberFormatException: For input string: "auto"
at java.lang.NumberFormatException.forInputString(Unknown Source) ~[?:?]
at java.lang.Integer.parseInt(Unknown Source) ~[?:?]
at java.lang.Integer.valueOf(Unknown Source) ~[?:?]
at org.opensaml.saml.ext.saml2mdui.impl.LogoUnmarshaller.processAttribute(LogoUnmarshaller.java:36) ~[opensaml-saml-impl-4.0.1.jar!/:?]
at org.opensaml.core.xml.io.AbstractXMLObjectUnmarshaller.unmarshallAttribute(AbstractXMLObjectUnmarshaller.java:224) ~[opensaml-core-4.0.1.jar!/:?]
at org.opensaml.core.xml.io.AbstractXMLObjectUnmarshaller.unmarshall(AbstractXMLObjectUnmarshaller.java:116) ~[opensaml-core-4.0.1.jar!/:?]
at org.opensaml.core.xml.io.AbstractXMLObjectUnmarshaller.unmarshallChildElement(AbstractXMLObjectUnmarshaller.java:337) ~[opensaml-core-4.0.1.jar!/:?]
at org.opensaml.core.xml.io.AbstractXMLObjectUnmarshaller.unmarshall(AbstractXMLObjectUnmarshaller.java:128) ~[opensaml-core-4.0.1.jar!/:?]
at org.opensaml.core.xml.io.AbstractXMLObjectUnmarshaller.unmarshallChildElement(AbstractXMLObjectUnmarshaller.java:337) ~[opensaml-core-4.0.1.jar!/:?]
at org.opensaml.core.xml.io.AbstractXMLObjectUnmarshaller.unmarshall(AbstractXMLObjectUnmarshaller.java:128) ~[opensaml-core-4.0.1.jar!/:?]
at org.opensaml.core.xml.io.AbstractXMLObjectUnmarshaller.unmarshallChildElement(AbstractXMLObjectUnmarshaller.java:337) ~[opensaml-core-4.0.1.jar!/:?]
at org.opensaml.core.xml.io.AbstractXMLObjectUnmarshaller.unmarshall(AbstractXMLObjectUnmarshaller.java:128) ~[opensaml-core-4.0.1.jar!/:?]
at org.opensaml.core.xml.io.AbstractXMLObjectUnmarshaller.unmarshallChildElement(AbstractXMLObjectUnmarshaller.java:337) ~[opensaml-core-4.0.1.jar!/:?]
at org.opensaml.core.xml.io.AbstractXMLObjectUnmarshaller.unmarshall(AbstractXMLObjectUnmarshaller.java:128) ~[opensaml-core-4.0.1.jar!/:?]
at org.opensaml.saml.metadata.resolver.impl.DOMMetadataResolver.initMetadataResolver(DOMMetadataResolver.java:68) ~[opensaml-saml-impl-4.0.1.jar!/:?]
at org.apereo.cas.support.saml.idp.metadata.locator.SamlIdPMetadataResolver.initMetadataResolver(SamlIdPMetadataResolver.java:64) ~[cas-server-support-saml-idp-core-6.3.2.jar!/:6.3.2]
at org.opensaml.saml.metadata.resolver.impl.AbstractMetadataResolver.doInitialize(AbstractMetadataResolver.java:289) ~[opensaml-saml-impl-4.0.1.jar!/:?]
at net.shibboleth.utilities.java.support.component.AbstractInitializableComponent.initialize(AbstractInitializableComponent.java:65) ~[java-support-8.1.0.jar!/:?]
at org.ape
I'm trying to configure CAS to warn about soon expiring ldap password. I already managed to get
accountState=[org.ldaptive.auth.ext.PasswordPolicyAccountState@1977058880::accountWarnings=[[org.ldaptive.auth.AccountState$De
faultWarning@1311510613::expiration=2021-08-18T11:53:02.663310Z[Etc/UTC], loginsRemaining=-1]], accountErrors=null]
to log, but how do I configure cas to warn the user when that happens?