Authentication with Guidewire Hub

When designing an application (for example, an Agent Portal) that calls InsuranceNow REST APIs, use the Guidewire Identity Hub integrated authentication via OAuth2 and JWTs.

About this task

Every caller application must be registered with Guidewire Hub. The information provided during the registration process varies based on whether the application is a browser-based application or a service application.

Procedure

  1. Determine which OAuth 2.0 flow the application will use. The auth flow must be one of the following:
    • Authorization code flow (browser-based app with JS client and trusted server)
    • Authorization code flow with PKCE (browser-based app with JS client and no trusted server)
    • Client credentials flow (server-to-server integrations; in InsuranceNow this uses a service account mapping for the client application).
    For more information, see Choose an OAuth 2.0 application flow.
  2. In the Guidewire Community, create a Support Task case using the GWHUB-0110 – Create, Update or Delete Guidewire Hub Application template and specify that you need an InsuranceNow REST API registration with Guidewire Hub using the desired auth flow.
    For more information, see .
    Guidewire sends you a list of required information based on the selected auth flow. Provide this information to Guidewire. Guidewire registers the application for OAuth based on the information provided. Guidewire will also send information to you that you need to further configure authentication, such as a client ID and client secret.

    Once you have the authorization information from Guidewire, you can proceed with authentication configuration.

    Note: For further information on the difference between auth code flow with PKCE and auth code flow with client secret, refer to Authentication with Guidewire Identity Federation Hub in the Guidewire Cloud Platform documentation set.