Skip to content

Conversation

@JanekBeck
Copy link

Closes #52

Copy link
Contributor

@jonkoops jonkoops left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We'll need some additional tests to verify this behavior works correctly.

@JanekBeck
Copy link
Author

We'll need some additional tests to verify this behavior works correctly.

I will look into it.
Unfortunately I could not get the test setup with Windows 11, WSL 2 and podman to work. The container starts and I can visit the Keycloak server url, but apparently Playwright can't do that.
Hopefully I can find a fix.

@jonkoops
Copy link
Contributor

I will look into it. Unfortunately I could not get the test setup with Windows 11, WSL 2 and podman to work.

There should be no need for Podman, to my knowledge, Playwright works natively on Windows.

@jonkoops
Copy link
Contributor

jonkoops commented Jul 8, 2025

Hi @JanekBeck, are you still interested in landing this PR? If so, could you rebase your work?

@JanekBeck
Copy link
Author

Sorry for taking my time. I will update this PR in a few days.

There should be no need for Podman, to my knowledge, Playwright works natively on Windows.

Podman is required on your setup to start a keycloak server

command: `podman run -p 8080:8080 -p 9000:9000 -e KC_BOOTSTRAP_ADMIN_USERNAME=admin -e KC_BOOTSTRAP_ADMIN_PASSWORD=admin -e KC_HEALTH_ENABLED=true --pull=newer quay.io/keycloak/keycloak:${KEYCLOAK_VERSION} start-dev`,

and the WSL does not allow access to this instance from Windows by default. I will try it with Linux.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Don't force token refresh when the token from init() isn't expired

2 participants