Sequence of Web Service Calls

The following image shows the sequence of web services calls:

  1. Communication is initiated by a client login API call.

    This call includes username, password, and the tenant.

  2. The OPE gateway forwards this call to the Auth Center service.
  3. The Auth Center service reads the Consul configuration located at /config/application/auth/userinfo to retrieve information for username, password, and tenant.
  4. The Auth Center service authenticates the request and generates the JWT with the following information:

    JWT is validation is controlled by Consul Keys /config/application/auth/jwtexpiration and /config/application/auth/jwtsecret.

  5. The client stores the JWT and passes this token as part of the Offer Search Engine and Model Loading Engine web service SOAP and REST calls.
  6. To access Model Loading Engine web services, client calls the OPE Gateway with the required web service payload along with the JWT.
  7. The OPE Gateway intercepts and validates the JWT.
  8. If valid, the tenant ID is extracted from the payload and the call is forwarded to the appropriate Model Loading Engine container.
  9. The response is forwarded to the OPE Gateway.
  10. The OPE Gateway forwards this response to the client.

When accessing TIBCO OPE, the flow of web services call is similar to that described in Steps 6 to Step 10.