Support multiple client_id values, per security definition

ui.initOAuth should support specifying configuration per-security definition. Specifically client_id and client_secret values.

My API has multiple security definitions available. But the Swagger UI has a different ClientID for each one (being that they are different providers). I am currently unable to use both without removing the client_id and specifying it manually in the textbox during authenticaiton.

[delboy1978uk]

Me too! I have one security definition for my oauth2 setup, which accepts all 4 oauth 2 grant types/flows. However, each flow has a differently configured client! It would be good if the initialisation function take both which definition you are referring to, and if an oauth 2 type, which flow we were talking about.

[pfeigl]

Here is btw. kind of a duplicate to it: https://github.com/swagger-api/swagger-ui/issues/4087 Someone started working on it, but it looks like it was never finished.

I’m actually wondering, that this did not get more feedback already. It’s such a common usecase, when different public (or internal) auth providers like Google, Microsoft, Facebook are accepted.

We even have legacy flows which do not need a client_id at all and the UI always sends the one which is setup globally.