Skip to content
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

Events expiration setting in realm.json is ignored during realm import" #1230

Open
aheeb opened this issue Dec 9, 2024 · 1 comment
Open
Labels

Comments

@aheeb
Copy link

aheeb commented Dec 9, 2024

Current Behavior

When I put eventsExpiration to 600 like here in the realm.json:

"eventsExpiration": "600"

It just gets ignored in keycloak itself because the newest keycloak version already has a default value for that. So right now, the default value of keycloak overrides my configuration. It only works if I delete the default value in the UI and then import it again.

Expected Behavior

When I put eventsExpiration to 600 like here in the realm.json:

"eventsExpiration": "600"

Keycloak should take it as the value for the user events expiration like in the screenshot down below
image

Steps To Reproduce

1. set eventsExpiration to 600
2. start the keycloak service
3. import the keycloak config

Environment

  • Keycloak Version: 24.0.5
  • keycloak-config-cli Version: 6.2.1
  • Java Version: 21

Anything else?

No response

@aheeb aheeb added the bug label Dec 9, 2024
@antikalk
Copy link
Contributor

Did you try setting eventsExpiration with a number value?

"eventsExpiration": 300

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants