Hi Jim… yes, a Session needs to re-authenticate with the broker upon reconnection.
I just tried to change the JCSMPProperty.PASSWORD of an existing Session, and it causes an exception to be thrown. I tried doing session.setProperty(JCSMPProperties.PASSWORD,"abc"); inside a JCSMPReconnectEventHandler, and it didn’t work.
But your use case is valid and interesting, so I’ll raise with the Solace team internally about pros/cons of implementing.
In the meantime, I think you will have to close() the Session, change the password property, and then recreate the Session and call connect() again… so, not exactly a reconnect, more of a “new connection”.