-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[defect]: Date parsing fails when using Redis cache #5304
Comments
On quick examination, it looks like the date is being saved as a string without spaces, but the parser seems to be expecting that the date is in quotation marks. The solution is likely to either print the full date string with spaces, or instead just print it as an integer. |
Also, which version of FreeRADIUS are you running? |
You're right! I've tried changing the ATTRIBUTE OAuth2-Password-Last-Modified 3000 string # instead of date and then adding quotes around the attribute:
Afterwards I've restarted everything and tested that it works correctly. Should I report this to the
The latest stable one from Dockerhub, i.e. FreeRADIUS version 3.2.3. |
What type of defect/bug is this?
Unexpected behaviour (obvious or verified by project member)
How can the issue be reproduced?
I've successfully configured the
freeradius-oauth2-perl
module module for authenticating with Microsoft Azure AD. Now I'm trying to get it to use Redis for cache, instead of the non-persistent in-memory cache.I've enabled the
redis
module and configured it and I've also updated thefreeradius-oauth2-perl/module
file:The first time I use
radtest
to authenticate, it works, and it creates a new cache entry in Redis:The cache entry (read directly from
redis-cli
) looks as follows:However, subsequent requests fail to access the cache:
The issue seems to be with reading back the cached date, which FreeRADIUS created in the first place. I'm guessing this issue is similar to #3602, but I haven't been able to determine why it's happening.
The text was updated successfully, but these errors were encountered: