Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following diagram displays the main components and actors involved in the flow.Eureka-211.drawio (1)-20240715-133046.pngImage Removed

Drawio
mVer2
simple0
zoom1
inComment0
pageId329154572
custContentId330170434
diagramDisplayNameEUREKA-211-1.drawio
lbox1
contentVer1
revision1
baseUrlhttps://folio-org.atlassian.net/wiki
diagramNameEUREKA-211-1.drawio
pCenter0
width1140
links
tbstyle
height908

Flow:

  1. mod-scheduler prepares a request and puts impersonated token for the system user into x-okapi-token request header. Then the request goes from mod-scheduler to its sidecar.

  2. Because Sidecar (mod-scheduler) has dynamic routing enabled and the requested route is not known, it calls the mgr-URLs to resolve the discovery information.

  3. mgr-URLs calls mgr-Tenant-Entitlements to resolve the actual module's version.

  4. mgr-URLs calls mgr-Applications to retrieve the actual discovery information that points to the Sidecar (Module A).

  5. Sidecar (mod-scheduler) dynamically routes the request to the Sidecar (Module A).

  6. Sidecar (Module A) authorizes the request to Module A.

    1. get token from request header

    2. parse token

    3. call Keycloak to evaluate permissions. Since the system user has access to all resources, authorization will be successful

  7. Sidecar (Module A) forwards the request to Module A for processing.

...