Example flow for services with service account mapping

The following diagram identifies the flow of authentication and authorization information for services with service account mapping. Colors are used in the following ways:

  • Orange - credentials information
  • Blue - endpoint access information
  • Green - resource access information
  • Red - proxy user and session user information

Some values are used to determine multiple types of access. These values initially appear as black (when they do not apply to a single type of access), and then later appear in one or more specific colors (to reflect the value is being used at that point in the process for a specific type of access).

In the following example, an API call is triggered by the Acme billing application, BillingApp.


Authentication flow for services with service account mapping
  1. When FNOLReporter triggers an API call, it must first request a JWT from Guidewire Hub. The request for the JWT includes the client ID (0oaqt9pl1vZK1kybt0h7), the secret (aSecret), and additional deployment information (tenant.acme, project.default, planet_class.prod).
  2. Guidewire Hub authenticates the services based on the client ID and secret.
  3. Guidewire Hub generates a JWT and sends it to the service. This JWT includes the client ID (cid) and additional deployment information.
  4. The service sends the API request to PolicyCenter along with the JWT.
  5. The IExpandTokenPlugin plugin is not relevant for services with service account mapping.
  6. PolicyCenter determines the endpoint access.
    1. First, PolicyCenter executes a lookup to map the client ID (0oaqt9pl1vZK1kybt0h7) to a service account name (acmebillingappuser).
    2. Then, PolicyCenter queries for the user roles that this account name has. One role is returned: acme_billingapp.
    3. Based on the returned role, the acme_billingapp.role.yaml API role file is used to define the endpoint access.
  7. Next, PolicyCenter determines the resource access strategy. Based on the fact that the service account lookup found a valid service account, PolicyCenter grants resource access as defined in the internal access.yaml files. (* PolicyCenter starts with internal_ext-1.0.access.yaml, but this file references additional access.yaml files whose name starts with "internal".)
  8. Proxy user access is not relevant for services with service account mapping.
  9. PolicyCenter processes the request.
    1. The session user is the service account: acmebillingappuser.
    2. The endpoint access is defined by acme_billingapp.role.yaml.
    3. The resource access is defined by internal access.yaml using the resource access ID of acmebillingappuser.
  10. PolicyCenter provides the response to the initial call.