add auth token in header on swagger pages

[JosefAssadERST]

In the swagger pages you get a very helpful text field with a "copy" button for the curl calls corresponding to the swagger example calls. Right now we have to manually figure out what the HTTP header for the token is, and fetch the token by hand from another page, and add it to that curl command.

Surely we can override or extend the swagger framework to inject that so the copied command can be invoked directly?

It's not a big deal but it's a fairly obvious and recurring paper cut.

[iszulcdeepsense]

Good reasoning.

Just want to note that in the current design, PUB is the authentication gateway and it's the last place where the auth token is present. So Fatman may not know who was calling and what token should be displayed. The token can't be rendered at page in advance since we don't know which user or ESC will be calling it, so it ought to be taken from the request

[JosefAssadERST]

Yeah I think we discussed before and it was hard for some reason and that's entirely fair. I wanted to note the paper cut though so in the worst case we're aware.

[LookACastle]

I've been looking at this for a little while, and I don't necessarily think it is feasible to fix on our end. The documentation says cookie authentication doesn't work for "try it out" requests - which is what we're dealing with here.

If we can't render it in advance and can't use cookies to persist the information, I'm at a loss for how we exactly are supposed to get the data from one end to the other.