Before Message Broker can initiate communication with FSM Cloud it must be authenticated.
...
Currently company management is not available in the FSM admin. Therefore, a small utility program - E4C Cloud Manager has been created, that helps in company management. Please note that cloud manager is independent on the message broker version. The program can be downloaded here:
| View file | ||
|---|---|---|
|
The concept of companies has been described in the FSM Architecture Overview (System Architecture). In a nutshell, each Cloud account needs at least one company to be configured. All messages are exchanged in context of the company. In order to manage companies, start E4C Cloud Management.exe and login with Cloud account and the corresponding password. Then on Companies tab you can create and remove companies.
...
Important note: be careful when deleting companies. When company is deleted, all data related to it is removed from the Cloud. This operation cannot be undone.
...
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
Access token
...
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.exe utility. After logging
...
in
...
(using FSM account name and account password) switch to the Access Token tab
...
consisting of input field and two buttons:
‘Generate Access Token’ - generates new access token. This also invalidates previously generated token if there was one. After closing the app, generated token will not be displayed ever more - application can generate it but it is not stored anywhere
‘Test Access Token' - checks validity of access token entered in the input field. When button is pressed application takes entered string and tries to authenticate to FSM with. If it is possible relevant message is displayed saying ‘Access token is valid’ otherwise it says ‘Access token is invalid’
Generated Assess Token can be copied to Message Broker configuration file.
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
There can only be one active authentication token per account. This means, that when a new token is generated, the old one |
...
becomes invalid. This may break communication, which already has been set-up. |
...
There should be only one connector (Message Broker instance) per Cloud account. It is highly recommended not to share the access token among several Message Brokers, as it may lead to unexpected behaviours.
...
With Cloud Manager three passwords can be encrypted:
SAP user
Message Broker user
Proxy
...
...
Client Id & Client Secret
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