Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

User is not removed using keycloak client

See original GitHub issue

scenario:

Create user “pepa” and add them to group recv_*
Verify that user has permissions to receive messages
Remove user “pepa”
Create user “pepa” and add them to group send_*
verify that user “pepa” does not have permissions to receive messages --> now fails

test reproducer is currently in branch “client-authz-tests”

make MULTITENANT=true SYSTEMTEST_ARGS='standard.authz.AuthorizationTest#testUserPermissionAfterRemoveAuthz' systemtests

Issue Analytics

State:
Created 6 years ago
Comments:7 (7 by maintainers)

Top GitHub Comments

1reaction

kornyscommented, Jun 19, 2018

@lulf I think I know where is an issue: looks like that user is not removed using keycloak client in systemtests,:

09:22:20,091 [main] INFO io.enmasse.systemtest.KeycloakClient - User 'pepa' will be removed
09:22:20,400 [main] INFO io.enmasse.systemtest.bases.TestBase - User pepa:pepaPa55 will be created
09:22:20,406 [main] INFO io.enmasse.systemtest.KeycloakClient - Waiting for realm brokered-shared-0 to exist
09:22:20,681 [main] INFO io.enmasse.systemtest.KeycloakClient - User 'pepa:pepaPa55' already created, skipping
09:22:20,689 [main] INFO io.enmasse.systemtest.KeycloakClient - Waiting for realm brokered-shared-0 to exist
09:22:20,974 [main] INFO io.enmasse.systemtest.KeycloakClient - Waiting for realm brokered-shared-0 to exist
09:22:21,276 [main] INFO io.enmasse.systemtest.KeycloakClient - User 'pepa' successfully joined group 'pepa_group'

0reactions

kornyscommented, Jun 20, 2018

fixed