Maia Iyer
Maia Iyer
This error comes upon configuration/startup of the backend; I believe the desired behavior is that the backend can try to connect a couple times and ultimately crash if it can't...
blocking for now - want to stabilize frontend build
from https://github.com/spiffe/spire-api-sdk/tree/main/proto/spire/api/server the following have to be added - [X] agent - [ ] bundle - [X] debug - [X] entry - [ ] svid - [ ] trustdomain
closing this issue; we will add SPIRE commands as needed or asked for. We have issues towards this work in #474 and #475
The major pain point of configuring federation seems to be due to the exchange step. Currently, this takes three steps: - Obtain a trust bundle from the source SPIRE server...
Okay! due to this comment and offline conversation, we will go with API-to-Role mapping with an additional constraint. We required defining the roles as well, so that an additional check...
I agree with all the cases you defined. For the fourth about API with no role reference, - I definitely vote to not do 1. We should default to least...
Hello! I think my main complaint here is that the different details of this error message were written a bit haphazardly and causes redundancy. For example, `Cannot configure auth plugin:...
blocked by #434
We execute two Golang subroutines in the backend, and we successfully propagate the errors to the main process. Additional good ideas would be to - [ ] Include other outputs...