Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TLS/certificate authentication not working if user/password is not set to null #30

Closed
kervoaz opened this issue Jul 27, 2019 · 2 comments

Comments

@kervoaz
Copy link

kervoaz commented Jul 27, 2019

  • ibmmq-jms-spring :2.1.2
  • Java version : oracle 1.8

Hello,
This issue looks like the closed issue "Empty/Blank passwords don't seem to work. #18".
If we use certificate as authentication mechnanism, properties user and password (ibm.mq.user /ibm.mq.password) must be set to null in properties file. If these properties are not declared in prop file, they are setup with dummy values(admin/passw0rd) which overwrite the certif authentication mechanism.
This behavior should be at least described in the documentation(if it is the expected behavior).
From my side, I have lost many time because in properties file, I have commented these 2 properties instead of define at null...:(

Thnaks
Regards

@ibmmqmet
Copy link
Collaborator

The README already mentions these properties to avoid password checking:

These attributes can be set to an empty value, to use the local OS userid automatically with no authentication (if the queue manager has been set up to allow that).

but I'll see if there's a reasonable way to further highlight it

@ibmmqmet
Copy link
Collaborator

README further updated in 2.2.0 release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants