nest-keycloak-connect
nest-keycloak-connect copied to clipboard
keycloak-nodejs-connect module for Nest
3.0
A few ideas that may come up in the next major version: ~~- [ ] Multi-tenancy support~~ (moved to 1.8.0 release) - [ ] Create permissions - [ ] Create...
I try to use Keycloak as Authorization Services. I want to secure the endpoints of my REST API with resources, scopes and permissions. The problem is, I get a 403...
Installing my project with Yarn 3, I'm getting the following warning: ```` ➤ YN0060: │ app-f43f79@workspace:app provides keycloak-connect (pb1244) with version 19.0.2, which doesn't satisfy what nest-keycloak-connect requests ➤ YN0000:...
I'm trying to build a custom guard to verify that the logger user is the same asking for resources belonging to him. For example, if I have a resource `/users/alice/cats`...
I'm using in multi-tenant mode with ```bearerOnly: true``` I've registered the module like this: import: ```javascript KeycloakConnectModule.registerAsync({ useFactory: (configService: ConfigService) => ({ clientId: 'test', secret: 'test', authServerUrl: configService.get('KEYCLOAK_SERVER_URI'), policyEnforcement: PolicyEnforcementMode.PERMISSIVE,...
As the title mentions, if you don't send the Access JWT as a Bearer Token in the Headers, the internal `const isAllowed = yield enforcerFn(keycloak, permissions);` returns false even if...
May not be a library specific bug, but after hours of investigation, I found that if you grant an Access Token from a client, you can't use it to handle...
Hello, I currently have a docker architecture with a nginx that serves as a reverse proxy, a nestjs backend and a keycloak, each on different containers and on the same...
Error: Nest can't resolve dependencies of the AuthGuard (?, KEYCLOAK_CONNECT_OPTIONS, KEYCLOAK_LOGGER, KEYCLOAK_MULTITENANT_SERVICE, Reflector). Please make sure that the argument KEYCLOAK_INSTANCE at index [0] is available in the CategoryModule context. Potential...
The role merger implemented in f540e4475008c1972876528763e3856411e08d52 and referenced in #127 does not work. With the configuration option `roleMerge: RoleMerge.ALL` and a class decorator `@Roles({ roles: ['role1'] })` and a handler...