Support multiple Auths in CallTemplates #55
Description
"Generally, have you considered returning more than one auth? In practice one API can have any number of auth middlewares and support multiple auth strategies at the same time. Between server and client there is a "strategy pattern": The server implemented auth, so he lists the auth strategies it provides. The client choses one of the auth strategies on its own preferences."
"Supporting multiple auths is also an interesting idea. Not sure how the choice would be made on which to choose, as the AI never sees anything auth related. But it's definitely a good point to bring to the discussion. Perhaps it just chooses the auth it has the credentials for. In that case, its a very good idea"
"I'm pretty sure that having multiple auths is critical, because APIs in the real world have multiple auths at the same time. Consider how this works in OpenAPI, where you can have many different security schemes (but it seems to be limited to one of the same "type", which makes sense to me): https://swagger.io/docs/specification/v3_0/authentication/"
Supporting multiple auths seems like an important step forward. Waiting for some proposals on how to best tackle this, and how to select the auth to use.