Can we shut down basic authentication at client user name level instead of VPN level. Suppose I want my client user name should use only certificate authentication and not basic authentication what should be the process ? By not giving password to client user name will solve the issue ?
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
. If my response doesn’t make sense for your topic, please react to it with a
.
Based on the provided documentation, I’ll explain whether basic authentication can be shut down at the client username level and address the password question.
Reasoning:
- Basic authentication is configured at the Message VPN level, not at individual client username level
- Client usernames can have passwords set or removed, but this only affects internal authentication
- Basic authentication must be enabled/disabled for the entire Message VPN using the
shutdownorno shutdowncommands - Not providing a password for a client username would only affect internal authentication mode, not basic authentication as a whole
Answer:
No, basic authentication cannot be shut down at the individual client username level - it can only be enabled or disabled at the Message VPN level. Not giving a password to the client username will not solve this issue because:
- Basic authentication is a Message VPN-wide setting that applies to all clients connecting to that VPN
- While you can remove a password from a client username, this only affects internal authentication scenarios
- The basic authentication scheme itself remains active as long as it’s enabled at the Message VPN level
If you need to control authentication for specific clients, consider:
- Using a different authentication scheme like client certificates or OAuth
- Configuring appropriate client profiles and ACL profiles to control access
- Using internal authentication where password settings can be controlled per username
For the complete details on configuring client authentication, see:
Configuring Client Authentication
Got it. If I give select basic authentication as Internal and not give password will my basic authentication for a client still work ?
Hi Nagamani,
The AI didn’t quite get it right. If you have basic authentication enabled with internal checking, if you don’t give the client a password, they will not be able to login. You can still create the client in the internal database and use it to authorize the client (assign the client profile and ACL profile).
Best Regards,
Paul