hard coded auth key leaking to new <action>
Opened this issue · 0 comments
starpit commented
origin: kubernetes-sigs/kui#468
I'm not sure why this is hardcoded - it's not really guaranteed to be true for local deployment and leads to surprising results.
On new x
, and then clicking deploy, the authentication header sent is this hard coded key even though auth add ....
was done explicitly. The best I can figure so far is that maybe this key is somehow leaking threre.