[Bug]: Connecting Event Portal to a runtime Event Broker: URL wrong?

[10100011]

Bug Description

In the CodeLabs exercise 'Connecting Event Portal to a runtime Event Broker', the EMA YAML connection file contains a URL which may have too many levels on line 84:

plugins.resources.connections.url: https://mr-connection-xxxxxx.messaging.solace.cloud:943/SEMP/v2/config

This results in an error on the EMA:

"diagnostic":{"severity":"error","summary":"SEMP call failed","detail":"request failed for https://mr-connection-xxxxxx.messaging.solace.cloud:943/SEMP/v2/config/SEMP/v2/config/msgVpns/rrrrrr using GET, No paths found for /SEMP/v2/config/msgVpns/rrrrrr, INVALID_PATH"

...and updates cannot be pushed to the Event Broker.

Altering the line to:

plugins.resources.connections.url: https://mr-connection-xxxxxx.messaging.solace.cloud:943

...restores the connection.

Expected Behavior

Updates to be pushed to the Event Broker

Steps to Reproduce

Follow the CodeLabs exercise 'Connecting Event Portal to a runtime Event Broker', in particular Step 6 to save and create a connection file.

Solace Broker version

10.10.1.112

Solace API

No response

Solace API version

No response

[jessemenning]

I believe this is due to the
https://mr-connection-xxxxxx.messaging.solace.cloud:943/SEMP/v2/config/SEMP/v2/config/msgVpns/rrrrrr

containing a duplicate SEMP/v2/config .

Several people have run into this, which springs from the fact that the URL form field should not contain the full path, only
https://mr-connection-xxxxxx.messaging.solace.cloud:943, as the rest is autogenerated.

I tried to head this off by including a warning when the URL is on https://codelabs.solace.dev/codelabs/ep-connect-ep-broker/?index=..%2F..index#2 (see bottom of page). I obviously didn't do it well enough. Do you have any suggestions, either on the codelab itself, or on the Event Portal GUI that would have been helpful?

[josephlanoux]

Thank you for raising this issue. I created a story in our backlog to add validation of the URL field.