Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 00:46
    apereocas-bot synchronize #4811
  • Apr 08 21:46
    apereocas-bot synchronize #4811
  • Apr 08 20:16
    apereocas-bot synchronize #4811
  • Apr 08 19:51
    codecov[bot] commented #4811
  • Apr 08 19:48
    codecov[bot] commented #4811
  • Apr 08 19:45
    codecov[bot] commented #4811
  • Apr 08 19:43
    codecov[bot] commented #4811
  • Apr 08 19:42
    codecov[bot] commented #4811
  • Apr 08 19:41
    codecov[bot] commented #4811
  • Apr 08 19:33
    codecov[bot] commented #4811
  • Apr 08 19:32
    codecov[bot] commented #4811
  • Apr 08 19:31
    codecov[bot] commented #4811
  • Apr 08 19:27
    codecov[bot] commented #4811
  • Apr 08 19:24
    codecov[bot] commented #4811
  • Apr 08 19:22
    codecov[bot] commented #4811
  • Apr 08 19:19
    codecov[bot] commented #4811
  • Apr 08 19:17
    codecov[bot] commented #4811
  • Apr 08 19:16
    codecov[bot] commented #4811
  • Apr 08 19:12
    codecov[bot] commented #4811
  • Apr 08 19:11
    codecov[bot] commented #4811
Mikel
@mikelasla

@mmoayyed tested 6.1.2 with same results, CAS sends the token to the user, but the token fails to load a form, instead loads the login form again
this is my relevant config (anonymizing some fields tougth)

cas.authn.pm.enabled=true
cas.authn.pm.ldap.type=AD
cas.authn.pm.ldap.usernameAttribute=userPrincipalName
cas.authn.pm.ldap.searchFilterUsername=(userPrincipalName={user})
cas.authn.pm.ldap.ldapUrl=ldap://...:389
cas.authn.pm.ldap.useSsl=false
cas.authn.pm.ldap.baseDn=OU=produccion,DC=...,DC=...
cas.authn.pm.ldap.searchFilter=(userPrincipalName={user})
cas.authn.pm.ldap.bindDn=...
cas.authn.pm.ldap.bindCredential=.....
cas.authn.pm.reset.mail.from=autenticacion.noreply@...
cas.authn.pm.reset.mail.attributeName=userPrincipalName
cas.authn.pm.reset.mail.text=Para recuperar su contrase\u00F1a siga las instrucciones de este enlace: %s
cas.authn.pm.reset.mail.subject=Solicitud de cambio de contraseña

cas.authn.pm.reset.mail.from=....
cas.authn.pm.reset.mail.attributeName=email
cas.authn.pm.reset.mail.text=Reset your password with this link: %s
cas.authn.pm.reset.mail.subject=Password Reset Request
cas.authn.pm.reset.expirationMinutes=10

spring.mail.host=....
spring.mail.port=25
spring.mail.username=....
spring.mail.password=....
spring.mail.testConnection=true
spring.mail.properties.mail.smtp.auth=true
spring.mail.properties.mail.smtp.starttls.enable=false

The most annoying thing is that nothing appears on the log, I've got trace level enabled

Mikel
@mikelasla
Also, if it's not working on 6.0.3 and neither on 6.1.2, that's it worth to test on intermediate versions?
Gary Windham
@windhamg
Hi folks, I'm working on a CAS 6.1.2 instance and am using the embedded Jetty container. Does anyone know if there are cas.properties configuration parameters for Jetty, similar to the ones for the embedded Tomcat container detailed at https://apereo.github.io/cas/6.1.x/configuration/Configuration-Properties.html#embedded-apache-tomcat-container ?
Misagh Moayyed
@mmoayyed
@windhamg yes checkout the spring boot documentation for appendix A and they should be there.
Misagh Moayyed
@mmoayyed
@mikelasla if by immediate you mean most recent, that depends. It's usually a good idea to test. Not everything is ported back to maintenance branches
Mikel
@mikelasla
@mmoayyed thanks for your response, I'm trying now to debug the error and see if I can understand better the situation
infinity202
@infinity202
@mikelasla the PM function via web interface seems to be missing some parts of code. If you do a request new password via email it works great. I tested it with version 6.2.
Mikel
@mikelasla
Hi @infinity202 , thanks for your response, sorry I didn't undertand, I'm new in this CAS world. I did some integrations in the past tought. what do you mean with "request new password via email"? .
infinity202
@infinity202
Hi @mikelasla , i am new too ;-) I tried the password management too with 6.2 and i noticed too that the webpages of the CAS server don't appear to handle the things correctly. But i noticed that requesting a new password via email does seem to work.
But maybe i didn't read or understand you question correctly....
Mikel
@mikelasla
@infinity202 I see, and how do you request that new password by mail?
infinity202
@infinity202

after that i ran into new errors/ problems. The "set new password" method doesn't work. It only works if you reset the password by sending an email to the user.
I follow this guide: https://apereo.github.io/2019/10/25/cas61x-password-management-jdbc/
my remarks:

  1. "# Password Reset Email Info" and "# Forgot Username Email Info" have their option values mixed up. If you want have forgotten your username the system should lookup your email address. If you want to reset your password you need to give your name in stead of email address IMHO
  2. expired login method fails to update the database table Users. It does store the old password in the history table.
  3. text above the input fields isn't quite clear on what to do.

This is what i found out at 23 november.

Mikel
@mikelasla
@infinity202 thanks again for your response, my use case has Active Directory as the user directory, I think jdbc is not an option for me
Cardo Kambla
@CardoKambla
Good evening! Has anybody implemented OAuth20/OIDC protocol in their CAS? I have implemented it and have wondered if there is some way possible to find the relation of the user (username) and token with the given information from the database. I know OIDC gives a id_token in a JWT form, where the username is but I would like to be separately.
Cardo Kambla
@CardoKambla
The reason behind it is that I have an application that uses currently Spring Security Authorization and Resource Server. I want to implement the Apereo CAS Authorization Server to work with Spring Security Resource Server. They(Auth and Resource server) would use the same database for selecting/updating/inserting oauth_tokens. The default Spring Security JdbcTokenStore uses two tables for tokens, while Apereo CAS OAuth2.0 uses only one. If I were to get the username somehow from the table, I would be able to write my own custom JdbcTokenStore for the Resource Server.
namedHK
@namedHK
hi,everybody,did github has some example about how to develop cas by "cas gradle overlay templates"
Cardo Kambla
@CardoKambla
Discard my question. I was approaching the issue in a wrong way. I should have used /introspect request from the resource server to validate my access token. Also the library I was using is deprecated, so I am upgrading from it now.
Also I noticed with OIDC protocol, when I do the /introspect request. The expiration value of the token is not correct. The documentation states "Integer timestamp, measured in the number of seconds
since January 1 1970 UTC, indicating when this token will expire,
as defined in JWT" for the expiration time of the token. CAS has a default value of 28800 which does not correspond to that field correctly. It should start from 1576762337.
Cardo Kambla
@CardoKambla
the /introspect issuedAt and expiredAt response values need to be checked, when you leave the default values on, then spring security 5.2 resource server will throw the error "java.lang.IllegalArgumentException: expiresAt must be after issuedAt"
even though /introspect says the token is active, Spring Security 5.2 resource server sees a error when constructing the token object in java. It checks if issuedAt/expiredAt is null or not and when they are not null, it will check if expiredAt value is after issuedAt
Scott Williams
@vwbusguy
We're working on upgrading from 5.3 to 6.1 and seem to have hit the snag here (https://groups.google.com/a/apereo.org/forum/#!searchin/cas-user/trusted$20device%7Csort:date/cas-user/1tQbjF8NEtI/dff9nxqOAgAJ), where trusted devices no longer work for MFA. We're using mfa-gauth with mongodb for trusted devices. Is there any potential workaround? I'm afraid we might have to delay our deployment over it.
Mikel
@mikelasla
@mmoayyed Struggling trying to find a interruption point on source code in order to investigate. I tried the most obvious ones, like InitPasswordResetAction doExecute method but seems like the problem is way outside pm code. Can you point me to a good point to start debuging the webflow here?
Misagh Moayyed
@mmoayyed
@mikelasla If you don't mind, you could please summarize the problem for me? there have been too many posts and I have sort of lost track of the history here. What are you trying to do, and what's is causing a problem?
millecentdix
@millecentdix
Hi, I'm running a CAS 5.3.14 on Tomcat behind Apache and I want to change my Apache configuration to do proxyHttp and not ProxyAJP beacuse I have timeout on AJP connection. I followed the blog post https://apereo.github.io/2018/01/05/cas-deployment-with-proxy/ but I still have the insecure notice
millecentdix
@millecentdix
@millecentdix Ok I solved my problem by add secure="true" on the Tomcat connector
Axhay
@Axhay
what is the latest updated stable cas version ?
when is the new updated version going to come up?
jiangyanfeng
@jiangyanfeng
ERROR [org.apereo.cas.web.flow.resolver.impl.mfa.GlobalMultifactorAuthenticationPolicyEventResolver] [resolveInternal:GlobalMultifactorAuthenticationPolicyEventResolver.java:72] - <No multifactor authentication providers are available in the application context to handle [mfa-radius]>
help!
Gary Windham
@windhamg

Hi all,

I'm testing CAS 6.1.2 in an external Jetty (9.4.24) container, and I've been running into an issue where CAS logs an error message like the following:

User limit of inotify instances reached or too many open files

Prior to a huge stack trace and the application shutting down.

I originally saw this issue when running the embedded Jetty container, then switched over to an external container to see if that would make any difference (it did not). I am running Jetty in a Docker container, and have increased the following sysctl parameters on the Docker host:

# sysctl -p
fs.inotify.max_user_watches = 560144
fs.inotify.max_user_instances = 512

I also have increased nofiles substantially, but that doesn't seem to have helped either.

Any ideas on where to begin looking to resolve this issue? I see CAS constantly logging messages like this: 2019-12-21 03:41:46,082 INFO [org.apereo.cas.util.io.PathWatcherService] - <Watching directory at [/etc/cas/config]>, which I assume to be related to the inotify issues.

Thanks!

Mikel
@mikelasla

Hi @mmoayyed, let me put some context

I'm trying to make Password Management work on 6.0.3 version against Active Directory. I also have another environment with OpenLDAP for testing. In both cases, auth works just fine, but PM doesn't.

Current behaviour is that PM correctly finds the user in the user directory and sends the token by mail.

https://myserver.my.domain/cas/login?pswdrst=eyJhbGciOiJIUzUxMiIsInR5cCI6IkpXVCJ9.ZXlKNmFYQWlPaUpFUlVZaUxDSmhiR2NpT2lKa2FYSWlMQ0psYm1NaU9pSkJNVEk0UTBKRExVaFRNalUySWl3aWRIbHdJam9pU2xkVUluMC4udzVOVk15NU9EeWsxS3JKSDZDYUREQS5neFMtbHROUVJxQ01MZEh5dFFyTWZrNEhpczB6Z29OZGd6eTdQeE5UeEYzVUoteTZPRm85VnpFQTdXV1RXR0ZRVURwbU0xRHZMQ1VPanRXTjlyMTFWYXZCVWwtSHlOdUY3RWFTVU93Y2tXTlRfVFlmbEdBQlJZTEpGUFBER0cyTXNIOXlUTlJ0MWoyNFYybUJpMnNibks1dnk2LW84eXRIR1FrRHZETkdOVEUyeXlsYnA4VmJaaTR4Skh6eGhKU00wd29SeWNGTERGNUhQN0pycVZ4RTVBLlUwek9pRWtGYkVXeXliVHFwYkhNUWc=.5Pswn-eqEwnDbGAqAVdbaCQRjsCKs1mWQcbWfGLJDLfExEnkcAeWicKwEx0PJk94FMQzjoYFLqv4e0Zguw_Mxg

But when I load the received URL, pswdrst urlParam seems to be ignored at all, regular login form gets loaded and no errors are shown in the logs, just this

https://pastebin.com/iTBaNTNA

This is the config for the OpenLDAP environment (replacing sensible values)

cas.server.name=https://myserver.my.domain
cas.server.prefix=${cas.server.name}/cas
server.port=443
server.ssl.enabled=true
cas.serviceRegistry.initFromJson=false
cas.serviceRegistry.json.location=file:/etc/cas/services
logging.config: file:/etc/cas/config/log4j2.xml
cas.authn.accept.users=
cas.authn.ldap[0].type=AUTHENTICATED
cas.authn.ldap[0].ldapUrl=ldap://myopenldapserver.my.domain:389
cas.authn.ldap[0].useSsl=false
cas.authn.ldap[0].baseDn=ou=People,dc=my,dc=domain
cas.authn.ldap[0].searchFilter=uid={user}
# https://apereo.github.io/cas/6.0.x/configuration/Configuration-Properties-Common.html#email-notifications
cas.authn.pm.enabled=true
cas.authn.pm.autoLogin =true
cas.authn.pm.policyPattern =^(?=.*[a-z])[A-Za-z\\d]{4,}
cas.authn.pm.ldap.type=GENERIC
cas.authn.pm.ldap.usernameAttribute=uid
cas.authn.pm.ldap.ldapUrl=ldap://myopenldapserver.my.domain:389
cas.authn.pm.ldap.useSsl=false
cas.authn.pm.ldap.baseDn=ou=People,dc=my,dc=domain
cas.authn.pm.ldap.searchFilter=(uid={user})
cas.authn.pm.ldap.bindDn=uid=somuser,ou=People,dc=my,dc=domain
cas.authn.pm.ldap.bindCredential=mypassword
cas.authn.pm.reset.mail.from=cas@my.domain
cas.authn.pm.reset.mail.attributeName=mail
cas.authn.pm.reset.mail.text=%s
cas.authn.pm.reset.mail.subject=Reset your password
cas.authn.pm.reset.securityQuestionsEnabled=false
cas.authn.pm.reset.expirationMinutes=10
cas.authn.pm.autoLogin=false
spring.mail.host=smtp.my.domain
spring.mail.port=25
spring.mail.username=cas@my.domain
spring.mail.password=caspassword
spring.mail.testConnection=true
spring.mail.properties.mail.smtp.auth=true
spring.mail.properties.mail.smtp.starttls.enable=false
Mikel
@mikelasla

@mmoayyed I also noticed this logs lines, so i pasted those propierties too

WARN [org.apereo.cas.util.cipher.BaseStringCipherExecutor] - <Generated encryption key [G3DuCmQupz-IC2TmAtl5dQrnz0EK0rQKOikWzzvM9Jg] of size [256] for [Password Reset Token]. The generated key MUST be added to CAS settings under setting [cas.authn.pm.reset.crypto.encryption.key].>

WARN [org.apereo.cas.util.cipher.BaseStringCipherExecutor] - <Generated signing key [lwrDVYc0vZ7Bl7FEqAnS7LbPPlMZ7xpaaz-d-1VRocox5praHqPC1hR1SNK8c8QtLaQqO933kReYoGVjpKNCYw] of size [512] for [Password Reset Token]. The generated key MUST be added to CAS settings under setting [cas.authn.pm.reset.crypto.signing.key].>

like that

cas.authn.pm.reset.crypto.signing.key=lwrDVYc0vZ7Bl7FEqAnS7LbPPlMZ7xpaaz-d-1VRocox5praHqPC1hR1SNK8c8QtLaQqO933kReYoGVjpKNCYw
cas.authn.pm.reset.crypto.encryption.key=G3DuCmQupz-IC2TmAtl5dQrnz0EK0rQKOikWzzvM9Jg
Cemal
@cmlonder
Alberto Perillo
@perillo3ro
Greetings
How can I add services to my CAS server?
I don't understood the docs
Alberto Perillo
@perillo3ro
I have a JSON file (that comes with CAS by default) that admit all https and imaps services to login with CAS, but when I try to login in CAS from an external service it returns "Application not allowed"
infinity202
@infinity202
You need to specify a service in a specific JSON file. The service is "just" the name of the service or corresponding url of the systems that is allowed to talk to the CAS server.
TonCherAmi
@TonCherAmi
Hi, I have a question regarding 6.* UI customization. In this post there's a mention of live-reload functionality being supported in 5.* via the build.sh script inside the overlay. As I understand that script is not a thing anymore having been replaced with gradle tasks. So my question is whether live-reload functionality is still present in 6.* and how I would go about getting it to work.
Cardo Kambla
@CardoKambla
I mentioned some time ago, that there is a problem with OAuth/OIDC /introspect request. When I get an access token from CAS and try to access some protected resource on my back-end, the /introspect request returns Unix Timestamp in seconds for issuedAt (iat) field (which is the expected behaviour) and expiresAt (exp) field has the configured value for accessTokens maxTimeToLiveInSeconds (default value 28800, which is not the expected behaviour, should also be unix timestamp). When Spring Security 5 tries to introspect the token, it sees that the expiredAt time is before the issued time and will throw a "IllegalArgumentException: expiresAt must be after issuedAt". When I checked the OAuth 2.0 token introspection standard, then it is stated that "exp" has to be of value "Integer timestamp, measured in the number of seconds since January 1 1970 UTC, indicating when this token will expire". TL:DR; OAuth/OIDC /introspect requests response value for expiresAt (exp) should be issuedAt + maxTimeToLiveInSeconds unix timestamp, currently it is just the maxTimeToLiveInSeconds value from CAS configuration.
This problem exists in version 6.2.0-SNAPSHOT and the resource server I am using for my back-end is Spring Security 5 OAuth2ResourceServer for introspection.
Cardo Kambla
@CardoKambla
I am gonna make a pull request on this but I still have not been able to test it yet, so it is gonna take some time for me until I get the pull request up.
Łukasz
@lgwozniak
I need to get to the site 'forgot password' directly, not from the login page. Is there any change to do that ?
chance*
pvemi
@vphanibhushanreddy
Has anyone ran in to this ? Am on CAS v 6.1.2 and Java 11
Caused by: org.apache.velocity.exception.ResourceNotFoundException: Unable to find resource '/templates/saml2-post-binding.vm'
at org.apache.velocity.runtime.resource.ResourceManagerImpl.loadResource(ResourceManagerImpl.java:474)
Cardo Kambla
@CardoKambla
OIDC /revoke requests seems to get "javax.persistence.TransactionRequiredException: Executing an update/delete query" when it tries to delete a ticket. There is a transactional annotation present in that class. Update requests seem to be working because the tickets are added to the database.
JackieTang
@tanghaojie
audit config?
any audit database config example?