Brandon Ingalls

I am also running into this issue on Boundary `0.11.0`. I'm trying to grant find-grained access to a specific target with a grant of ``` id=ttcp_lmhDHjOLmR;actions=read,authorize-session ``` This one does...

@malnick I was able to reproduce the issue from scratch inside of a docker-compose example. ``` # make a working directory to test [~]$ mkdir /tmp/issue # Navigate to this...

I followed the steps I detailed in https://github.com/hashicorp/boundary/issues/1603#issuecomment-961560891 but updated the docker image for boundary to `0.7.6`. ``` [/tmp/issue]$ docker-compose up boundary Creating issue_boundary_1 ... done Attaching to issue_boundary_1 boundary_1...

> @BrandonIngalls did this fix your issue? If so we will close this ticket. It did, but instead of just closing the ticket would it make sense to add some...

I also imported my key using gpg, so `gpg -K` also shows my private key, and I am still having the same issue on my laptop.

http://hastebin.com/cudopeniku.coffee

I think that pr is to move away from using methods in the datetime package that have been deprecated as of python 3.12 https://blog.miguelgrinberg.com/post/it-s-time-for-a-change-datetime-utcnow-is-now-deprecated

> its been months with this regression, so we changed our oidc provider to keycloak, not an issue anymore for us. Thanks for the suggestion, keycloak looks like it will...

Coming up on a year of Vault's OIDC feature being broken (v1.16.0 was tagged 2024-03-26).