Admin Credentials vs. Messaging Client Config Alternative credentials   

I have configured SIBus explorer to communicate to a WAS ND 6.1.0.23 cell. I have secured the SIBus, and have only System and a user bususer bound to the Bus Connector role. Global, Application, and Bus security are enabled. The Bus is permitting only transports using SSL.

For my SIBus Explorer configuration, I specified the WAS Primary Administrative Server userid ( websphere in my case) as the Admin Credentials, so that SIBus can connect to the DMgr's SOAP port. I exchanged certificates with the CellDefaultTrustStore

I also configured the Remote Messaging chain name to use the BootstrapSecureMessaging chain and SIB_MQ_ENDPOINT_SECURE_ADDRESS port on my App server (with the ME). I specified bususer and my remote messaging user name.
I am able to connect to the SIBus, and read messages on my various queues.

This all works, but when I specified a bususer1 - a userid that does not exist in my registry - as my SIBus explorer Remote Messaging User Name I am still able to connect and read the messages.

Without the correct Admin userid, I am unable to connect via the AdminClient to the Dmgr, but why is my "Alternative credentials" not being used? I don't believe that the "Alternative credentials" are being used at all, and that my connection and read of the queued messages are successful because I am connecting to the SOAP endpoint with a WAS Administrator role userid.

Martin Lansche