Scenarios

Description

ROMA Connect service integration involves the following development scenarios:

• API calling authentication: When a service system calls an API opened by APIC and the API uses App or IAM authentication, API calling authentication should be developed for the service system to add authentication information to the API request.
  • App authentication (with a signature): The service system integrates the ROMA Connect SDK to sign API requests.
  • IAM authentication (with a token): The service system obtains the authentication token from the cloud service and secures the API request with the token.
  • IAM authentication (with an AK/SK pair): The service system integrates the ROMA Connect SDK to sign API requests.
• Custom backend: When you create a function or data backend using an APIC custom backend, function scripts or database execution statements should be compiled.
  • Function backend: Compile function scripts to develop functions. ROMA Connect has provided some Java functions for your reference.
  • Data backend: Compile execution statements to perform operations on the data source.
• Backend service signature verification: If an API is bound to a signature key on ROMA Connect, the request sent by ROMA Connect to the backend service of the API carries the corresponding signature information. The backend service of the API must integrate the SDK provided by ROMA Connect and verify the signature information in the request.