Hi @Qais,
I went through the steps you outlined to make sure there werenât any steps missing and it worked successfully for me. It seems weird that you are in a state of SessionDisconnectedâŚthat error sounds like it would be caused by the app losing connectivity to the broker vs. a username/password or ACL permissions issue. Any chance youâre having network issues or think something could be preventing the connection from staying up?
When it comes to testing out if itâs an ACL issue it would actually be more useful if you could use the âTry Me!â menu option within the Broker Web UI itself. You can get to it by choosing the âManage Serviceâ button at the top right side of the Solace Cloud Console when within a Message Service. It has a few more features than the CodePen one and will give you an error that says âSubscription ACL Deniedâ if you try to subscribe to a topic that your client-username doesnât have permission to listen on.
Hi Marc, thank you for your prompt reply!
I tried it in the "Try Me!) Web UI. The Connection does not fail but it keeps trying to connect for hours. With no success of connecting.
I am not sure about the password I enter. Do I reuse the password from connect->Solace Web Messaging->password (see attachment)
. ? I mean when I create a âClient Usernameâ under Manage â Access Control â Client Usernames and try to use this Client Username during âTry Meâ connection, do I need a new password or I can use the one from the solace web messaging (in the attachement)?
Hi @Qais,
You should be able to use any client-username that you setup under âManage â Access Control â Client Usernamesâ or the default solace-cloud-client that youâd find under Solace Web Messaging. It definitely shouldnât take a long time to connect. Can you purposefully try an incorrect password and see if you get a âThe username or password is incorrectâ error or if it just continues to spin?
If you donât get the error can you open the console in your browser and see if there are any errors that might hint at the issue?
I get now âThe username or password is incorrectâ . I know for certain that the password is correct and the username is just as in the client-username. Weird
You could try resetting the password to your new test-username client username, just to make sureâŚ? In the PubSub+ Manager, under Access Control â Client Usernames â edit your new one, and hit the âchange passwordâ. Not sure if that will help. Otherwise, to narrow down the issue, try changing the ACL Profile for your test-username back to the default ACL Profile, just to allow you to pub/sub from any topic⌠just as a test. But that shouldnât impact your connectivity.
BTW, does using the default pre-filled-in values (âsolace-cloud-clientâ) username and stuff work every time? No issues connecting?