Before Message Broker can initiate communication with FSM Cloud it must be authenticated. There are currently two supported ways of authentication:
using Access Token- this method is already considered as obsolete and will only be supported by Message Broker 3.X
using Client Id & Client Secret - this is a recommended way of authentication and will be supported by Message Brokers starting with Message Broker 4.0
...
For message brokers older than 4.0 an Access Token is an obligatory factor required to access the FSM Cloud. It can only be generated with use of the E4C Cloud Management.exeManager utility. After logging in (using FSM account name and account password) switch to the Access Token tab consisting of input field and two buttons:
...
Client Id & Client Secret
| Status | ||||
|---|---|---|---|---|
|
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Client Id and Client Secrete can be used with Message Broker starting with version 4.0 |
Currently recommended way of authentication to FSM is with use of Client Id and Client Secret. These can be generate in the FSM Admin portal.
On the account level navigate to ‘Clients’ section
Select ‘Create’ option
A new Client Id will be immediately generate. Make sure Active and ERP Connector checkboxes are ticked. Selected Authentication Method must be set to ‘Client Secret' like in a picture below and then press SAVE.
After new Client was created a Client Secret gets displayed in a screen like this one below
Client Id and Client Secret can be copied now to a Message Broker Configuration file
...
| panelIconId | atlassian-warning |
|---|---|
| panelIcon | :warning: |
| bgColor | #FFF0B3 |
...