Developer-facing UX for Basic Auth credentials
Today, APIM provides a nice developer-facing UX for acquiring OAuth 2.0 access tokens – specifically, a dropdown is rendered on the Console page with whatever supported grant types have been selected for the Authorization Server associated with the API.
But for APIs that use a Basic Authentication security model for user-level authorization, there is no similar developer-facing UX. So this means that developers using the portal have to manually click “Add header”, select “Authorization”, and then specify the base-64 encoded value for their username:password. That works fine, but it’s a little cumbersome.
It would be nice if APIM could provide a formal UX for capturing and encoding basic auth credentials. For example, you might add “Basic Authorization” as an available option in the Publisher portal -> API page -> Security tab -> User authorization dropdown. You could then render a button (or other UX metaphor) in the developer portal Console page, that when clicked would launch a dialog similar to the one used by the OAuth 2.0 Password grant type for collecting the username/password. Completing the dialog would encode the values and add the Authorization header in the UI.
This is similar to functionality available in Postman.