Configure Authentication Schema (OAuth) With Username/Password & Grant Type?

Solace Event Broker
,
1

Hi Solacers,

I’m trying to configure an authentication schema in Solace for an OAuth server. Currently, the UI only provides fields for:

  • clientId

  • clientSecret

  • Token Endpoint

  • Scope

However, I would like to configure username, password, and grant type as part of the OAuth setup — these options do not appear in the UI.

Is there any way to configure OAuth with username/password (e.g., Resource Owner Password Credentials grant)?

Any guidance or examples would be greatly appreciated.

image
image1538×1012 40.8 KB

image
image1590×242 8.89 KB

2

Hi there, I’m Solly AI, I generate responses to your questions using the power of the Solace Agent Mesh:

Please remember that AI technology can make mistakes so ensure that you read our Disclaimer.

AI Generated responses are a work in progress, your help in evaluating my response would be awesome! If my response makes sense, please mark it as a solution or give a :+1:. If my response doesn’t make sense for your topic, please react to it with a :shaking_face:.

Looking at the documentation, I can explain how to configure OAuth authentication with username/password (Resource Owner Password Credentials grant) on a software broker:

The key steps are:

  1. Create and configure an OAuth profile:
- Create an OAuth profile with `oauth-role` set to `resource-server`
- Configure the required endpoints (discovery or individual endpoints)
- Set client ID and client secret
- Configure username claim name and authorization groups claim name
  1. Configure the resource server settings:
- Enable parse-access-token if using JWTs
- Configure required audience, issuer, scope as needed
- Set validation options for audience, issuer, scope, and type
  1. Configure authorization:
- Set up authorization groups claim name to map OAuth groups to ACL profiles
- Configure access levels for the OAuth groups

However, I should note that the Resource Owner Password Credentials grant type is deprecated according to OAuth 2.0 specifications. The documentation recommends using alternative flows like:

  • Authorization Code grant with PKCE for user authentication
  • Client Credentials grant for machine-to-machine authentication

For the specific configuration steps and commands, please refer to:

I recommend reviewing these sources to determine the most appropriate OAuth flow for your use case, since password grant is no longer recommended.