Document issue type
Type/Bug (Report inaccuracies, outdated information, or missing details in the existing content)
Description
- In IS-7.0.0, IS-7.1.0, and IS-7.2.0 supports custom HTTP based SMS provider configuration.
- The UI configurations don't have a specific field to configuring authorization details
- What supported is, configure relevant Authorization header under
Headers section along with other headers
eg:
If using basic auth -> Authorization: Basic <base 64 encoded username:password>
If using bearer token -> Authorization: Bearer <obtained token>
https://is.docs.wso2.com/en/latest/guides/notification-channels/configure-sms-provider/#:~:text=at%20the%20runtime.)-,Headers,-Custom%20static%20headers
Having the explaination clearly on how to configure Authorization header in both of these common cases would be easier to understand for the user
Version
IS-7.0.0, 7.1.0, 7.2.0
Document issue type
Type/Bug (Report inaccuracies, outdated information, or missing details in the existing content)
Description
Headerssection along with other headerseg:
If using basic auth ->
Authorization: Basic <base 64 encoded username:password>If using bearer token ->
Authorization: Bearer <obtained token>https://is.docs.wso2.com/en/latest/guides/notification-channels/configure-sms-provider/#:~:text=at%20the%20runtime.)-,Headers,-Custom%20static%20headers
Having the explaination clearly on how to configure Authorization header in both of these common cases would be easier to understand for the user
Version
IS-7.0.0, 7.1.0, 7.2.0