Lauri Võsandi
Lauri Võsandi
Homebrew applications could use a unified method for showing navbar in the application to simplify navigation between microservices. Perhaps the easiest is to include navbar info in an OIDC claim...
Regular user accounts would have `type: person` attribute Service accounts would have `type: service` attribute which would modify the behaviour as following: * Impersonation as service user should be possible,...
Either add `allowedUsers` attribute to OIDCGWClient spec or include a username derived string in the groups claim (that does not collide with any existing ones). In the latter case it...
Currently user is shown `You need to be a member of an allowed group to access this resource` Add configuration option to allow requesting access to a group in the...
Tried executor 1.23.1 yet nothing gets written into `--cache-dir`
The `!trap` response sentence should raise Python exception. We're dealing with various Mikrotik devices and all the commands are not equally available on all the devices. Instead of crashing with...
I think `redirect_uri did not match any of the client's registered redirect_uris` is not very helpful for nailing down the issue. Perhaps include the strings in the error message so...
Passmower could be used to build IAM stack in a cloud native declarative manner. In other words execute HTTP(S) requests when various events happen on the user management side and...
The Passmower should have a stage where user is disabled before eventual complete user removal. This is particularly useful to implement GDPR compliance request. User disabled: * OIDC user remains...
Many (most) OIDC clients will need user object to exist before API calls can be performed with the user account. Some software solutions include SCIM user provisioning, see [here](https://learn.microsoft.com/en-us/entra/identity/app-provisioning/use-scim-to-provision-users-and-groups) how...