Hello @erol.komac

According to section 2.8.4 in the link above:

"the application should authenticate once to the EDP gateway. It is up to the application to distribute both refresh and access tokens to all threads/devices using the same machine credentials to connect to ERT Cloud.

The application should obtain a new token periodically from the EDP Gateway using the refresh token, as mentioned in Section 2.8.3. Upon response from the EDP Gateway, the updated access token should be shared within the application so that each of the connections made to the ERT Cloud can supply this common access token in the login/login reissue request message."

That means only one thread or one OmmConsumer using a user(machine) credential can request token from EDP gateway. Several OmmConsumers or multiple threads / connections requesting token with the same user do not work.

Moreover, OmmConsumer does not manage authenticate to EDP gateway. This is performed by its underlying API,ETA ValueAdd. If you use several OmmConsumers with the same user, each ETA ValueAdd requests access token and this will cause problem. Based on my experience, I suggested the client to uses a single OmmConsumer with batch request which can specify multiple RICs in a single request. Otherwise, you need to modify EMA, ETA Value add source code to share access token to the other OmmConsumers.

@erol.komac

In my opinion:

To share the token with multiple consumers, the application needs to directly get the token from the EDP gateway. Then, you need to configure consumers to connect to a host on ERT in Cloud with an encrypted connection. Each consumer needs to send a login request which contains the token to ERT in Cloud, and reissue the login request with the new token before the previous token is expired.

In short, instead of relying on session management feature in the Elektron SDK to obtain a token, query service discovery, and reissue a login request, developers may need to implement their own functions inside the application to manage token.