Signed instance identity / IAM / instance "service accounts"

I am looking into methods to automatically let my incus instances authenticate to openbao.

I think the holy-grail type solution would be if Incus acts as an oidc provider providing signed tokens via the instance API, allowing a deployment scenario similar to: kubernetes | OpenBao

However unless I am very mistaken that is currently not possible or in development, at least I couldn’t find it documented or in a ticket.

So I am curious about two things:

  1. Anyone who can point me to other mechanisms for establishing instance identity that could work here?

  2. I may experiment a bit with getting it to work myself in the coming year, would you guys be open to have something like this contributed eventually? Not anytime soon, to be clear :sweat_smile: .

Thanks

You could use /dev/incus/sock from inside the container/VM to access a user.XYZ configuration key set in the Incus instance config. That could then contain some signed blob or similar that the instance will be able to retrieve and forward to prove its identity.