DeactivateRbacSubjectViaPut
Tests
| Test |
Duration |
Result |
| deactivatedGroup_noLongerTakesEffectViaJwtGroupsClaim() |
0.237s |
passed |
| deactivatedUser_canNoLongerUseTheApi() |
0.195s |
passed |
| subjectNameCanBeReusedByANewUuidAfterDeactivation() |
0.265s |
passed |
Standard output
2026-08-10T16:32:38.660Z WARN 374 --- [o-auto-1-exec-6] o.h.engine.jdbc.spi.SqlExceptionHelper : SQL Error: 0, SQLState: P0001
2026-08-10T16:32:38.660Z ERROR 374 --- [o-auto-1-exec-6] o.h.engine.jdbc.spi.SqlExceptionHelper : ERROR: [401] subject tst-user_1786379558478 given in `base.defineContext(...)` does not exist or is deactivated
Where: PL/pgSQL function rbac.determinecurrentsubjectuuid(character varying) line 11 at RAISE
SQL statement "select rbac.determineCurrentSubjectUuid(currentSubject)"
PL/pgSQL function base.contextdefined(character varying,text,character varying,character varying,text) line 16 at SQL statement
SQL statement "call base.contextDefined(currentTask, currentRequest, currentSubject, assumedRoles, currentSubjectGroups)"
PL/pgSQL function base.definecontext(character varying,text,character varying,text,text) line 23 at CALL