mburt
04/14/2025, 1:39 PMexpiration:1
) and refresh (refreshExpiration:720
) tokens (enableRefreshTokens:true
), and I’m using annotation-based security on the handler.
What I’m noticing is that both the access and the refresh token can be used to access the function. So even once my access token is expired and returns a “expired” response, I can still pass the refresh token and get a full response.
If the two can be used interchangeably to access a secured route, what is the benefit of using refresh tokens at all? Couldn’t I just set the expiration of my access token to 720 and be done.coldfusioneer
04/14/2025, 4:25 PMbhartsfield
04/14/2025, 5:08 PMJeff
04/14/2025, 5:40 PMlaslo7
04/14/2025, 8:15 PMbdw429s
04/17/2025, 9:09 PMadam.euans
04/21/2025, 12:52 PMError: InvalidSignatureException: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.
Matt Dyer
04/22/2025, 5:34 PMMarco
04/22/2025, 6:38 PMDana Kowalski
04/22/2025, 9:59 PMseandaniels
04/23/2025, 8:45 PMDaniel Mejia
04/23/2025, 10:36 PMbhartsfield
04/24/2025, 2:54 PMjq 'del(.devDependencies)' /app/box.json > /tmp/box.json && mv /tmp/box.json /app/box.json
No big deal really, I'm mostly just curious if I am missing built-in functionality in commandbox.elpete
04/24/2025, 5:08 PMbox install —production
Chase Lane
04/25/2025, 1:46 AMPatrick Roy
04/28/2025, 8:35 AMbox install rabbitsdk
it seems to install rather old amqp-client-5.9.0. Could this safely be updated to latest 5.25.0 ?
2. Is this check for still needed on ModuleConfig : https://github.com/Ortus-Solutions/RabbitSDK/blob/development/ModuleConfig.cfc#L34 We're running on Lucee 6.0.3.1. I commented out that block of code from that ModuleConfig.cfc and started Lucee web server. Start a consumer... published ... got processed. The restarted Lucee and just re-published something to Rabbit : got processed. So.. not sure if and how that fileDelete is needed even? If one can explain, time permitting? Much appreciated! Thanks.
cc. @bdw429sphilcruz
04/28/2025, 10:41 PMfmdano
04/30/2025, 2:57 PMScott Steinbeck
05/01/2025, 1:22 PMJim Priest
05/01/2025, 1:33 PMJohn Liljegren
05/02/2025, 2:49 AMChase Lane
05/02/2025, 3:27 AMfmdano
05/02/2025, 3:11 PMgavinbaumanis
05/04/2025, 8:40 PMcubortea
05/05/2025, 8:37 AMjdk11-3.13.0
.)
After upgrading, I keep getting the following error:
> "There is no default object cache defined, you need to define this default cache in the Lucee Administrator."
When I check the Lucee Admin, the default object cache setting is empty, even though it worked fine in Lucee 5. It seems like my existing config.json
is not being properly loaded in Lucee 6.
Here’s the relevant part of my config:
"caches": {
"sst_XXX": {
"class": "ortus.extension.cache.redis.RedisCache",
"storage": "true",
"custom": {
"idleConnections": "5",
"maxConnections": "99999999",
"host": "hosyredis.ccc",
"port": "6379",
"keyprefix": "ref-cache",
"useSSL": "false",
"password": "",
"timeout": "10000"
},
"default": "object"
}
},
"cacheDefaultObject": "sst_XXX"
Has anyone encountered this before or found a way to fix it in Lucee 6?
Any help would be appreciated!Tim Badolato
05/05/2025, 3:47 PMFROM ortussolutions/commandbox:lucee5-3.13.0
RUN box install lucee@5.4.7.3
RUN box server set app.cfengine=lucee@5.4.7.3
And my box.json:
{
"VERSION": "1.4.5",
"SLUG": "CFWheels",
"TYPE": "mvc",
"dependencies": {
"cfwheels-bcrypt": "1.0.2",
"lucee": "5.4.7.3",
"s3sdk": "^5.7.1+94"
},
"installPaths": {
"cfwheels-bcrypt": "plugins/bcrypt/",
"s3sdk": "modules/s3sdk/"
}
}
docker-compose.yml:
wheelie_cfml1:
container_name: cfml
restart: always
build: "."
ports:
- "8080:8080"
- "8443:8443"
- "44307:44307"
environment:
CFENGINE: lucee@5.4.7.3
I'm having trouble upgrading my Lucee version. When I dump the current running version I see that I'm on 5.4.6.9 instead 5.4.7.3:
loaderPath string /usr/local/lib/serverHome/WEB-INF/lib/lucee-5.4.6.9.jar
Any idea how to fix this?seandaniels
05/06/2025, 6:10 PMseandaniels
05/06/2025, 8:09 PMdanmurphy
05/06/2025, 10:46 PMsrc="/includes/images/Dashboard.ico"
. For some reason, it tries to load this as <http://localhost:10000/includes/images/Dashboard.ico>
instead of https:/servername/includes/css/app.css
so it fails and the image doesn’t load. This happens with all included css files, js files, images, etc. If we do a fwreinit, they all load properly because they load via the server name and no port. We can’t seem to recreate this, it just seems to happen randomly. Any thoughts on what might be happening?Chase Lane
05/07/2025, 1:25 AM