This content is also valid for mrg-m-3.0.0 and shall be incorporated to the 3.0 MCIG.

Change also applied in MRG 3:

http://deathstar1.usersys.redhat.com:3000/builds/18173-Messaging_Installation_and_Configuration_Guide/index.html#Configure_SASL_using_a_Local_Password_File

(In reply to Joshua Wulf from comment #2)
> Change also applied in MRG 3:
> 
> http://deathstar1.usersys.redhat.com:3000/builds/18173-
> Messaging_Installation_and_Configuration_Guide/index.
> html#Configure_SASL_using_a_Local_Password_File

The above mentioned chapter is not related to the bug description. These bug is related to SSL python client setup. I would expect a new chapter "Enable SSL in Python Clients" (like in MCIG for MRG 2.x). The description is still missing in the 3.x documentation.

-> ASSIGNED

Sorry, my bad - that was the wrong link!

Try this one: http://deathstar1.usersys.redhat.com:3000/builds/18173-Messaging_Installation_and_Configuration_Guide/index.html#Enable_SSL_in_Python_Clients1

The content looks good now, only one issue here:

As mentioned in the bug description above (point 2.), the following sentence is no longer valid:
"Server authentication is not supported."

I'd suggest the following change:

<<<
"The Python client has some limitations in SSL functionality.

Server authentication is not supported. Python clients support authentication with SSL, with some caveats:

The Python clients ..."

>>>
"The Python client has some limitations in SSL functionality:

Server authentication must be demanded, client name must be explicitly provided when using EXTERNAL SASL mechanism for authentication.

The Python clients ..."

Thanks!

Updated: http://deathstar1.usersys.redhat.com:3000/builds/18173-Messaging_Installation_and_Configuration_Guide/index.html#Enable_SSL_in_Python_Clients1

Thakns for the update. Content approved.

-> VERIFIED