You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Twilio OpenAPI specification's current securitySchemes definition only includes the accountSid_authToken scheme for HTTP Basic Authentication, which uses accountSid and authToken for authorization. While this is a valid method, Twilio also supports API Key based authentication (using accountSid, apiKey, and apiSecret), which is not reflected in the current OAS. twilio_api_v2010.yaml
This omission leads to a gap in the authentication mechanisms available in generated SDKs or connectors.
Is there any specific reason behind the exclusion of API Key based authentication from the security schemes? Additionally, would you consider updating the OpenAPI specification to include this authentication method?
The text was updated successfully, but these errors were encountered:
Issue Summary
The Twilio OpenAPI specification's current
securitySchemes
definition only includes theaccountSid_authToken
scheme for HTTP Basic Authentication, which usesaccountSid
andauthToken
for authorization. While this is a valid method, Twilio also supports API Key based authentication (usingaccountSid
,apiKey
, andapiSecret
), which is not reflected in the current OAS. twilio_api_v2010.yamlThis omission leads to a gap in the authentication mechanisms available in generated SDKs or connectors.
Is there any specific reason behind the exclusion of API Key based authentication from the security schemes? Additionally, would you consider updating the OpenAPI specification to include this authentication method?
The text was updated successfully, but these errors were encountered: