Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Set up the Guidewire spoke

Integrate the ServiceNow instance and Guidewire using basic Auth or OAuth 2.0 authentication to authenticate ServiceNow requests.

Before you begin

  • Request an Integration Hub subscription.
  • Activate the Guidewire spoke.
  • Choose and implement the Guidewire authentication approach appropriate for your application. See the Guidewire documentation for Choosing an authentication flow for details.
  • Ensure that the dependent plugins are activated.
  • Role required: admin.

Register Guidewire as an OAuth provider

Use the information generated during the Guidewire application configuration to register Guidewire as an OAuth provider. OAuth provider registration enables the ServiceNow instance to request OAuth 2.0 tokens.

Before you begin

  • Role required: admin
  • Client ID and client secret generated from configuration of the third-party Guidewire application

Procedure

  1. Navigate to All > System OAuth > Application Registry.

  2. Select New.

    The system displays this message: What kind of OAuth application?.

  3. Select Connect to a third party OAuth Provider.

  4. On the form, fill these values.

  1. On the form header, select Submit.

Create OAuth 2.0 credential record for the Guidewire spoke

Create credential records to the Guidewire custom OAuth application you created during Guidewire account configuration. The Guidewire spoke connection and credential aliases use these credentials to authorize actions in Guidewire application. The Guidewire connection and credential alias uses these credentials to authorize actions.

Before you begin

Role required: admin

The following example shows the steps for creating a credential record for Guidewire PolicyCenter, Guidewire ContactManager, or Guidewire ClaimCenter.

Procedure

  1. Navigate to All > Connections & Credentials > Credentials.

  2. Select New.

    The system displays this message: What type of Credentials would you like to create?

  3. Select OAuth 2.0 Credentials.

    The pop-up window displays a blank OAuth 2.0 Credentials form.

  4. Enter these values.

FieldDescription
NameName to uniquely identify the record. For example, enter: `Guidewire OAuth`
Client ID<Client ID> created during the Guidewire account configuration.
Client Secret<Client Secret> created during the Guidewire account configuration.
Authorization URLOAuth authorization code endpoint.
Token URLOAuth server token endpoint.
Token Revocation URLOAuth server token revocation endpoint.
Redirect URLOAuth callback endpoint in this format: `https://.service-now.com/oauth_redirect.do`
OAuth API ScriptScript to customize the request and response.
Logo URLURL that contains an image to use as the application logo.
Default Grant TypeGrant type used to establish the token..
Refresh Token LifespanTime, in seconds, that the refresh token is valid. The default time is 8,640,0000 seconds.
PKCE requiredOption to enable public clients to require PKCE for an authorization.Note: You can use only Authorization Code as the Default Grant type when PKCE is enabled.
ApplicationApplication scope that contains this record.
Accessible fromApplication scope that this registry is accessible from.
ActiveOption to actively use the application registry.
Use mutual authenticationOption to use mutual authentication for token request and revocation. This option requires a mutual authentication profile to be specified.
Send credentialsOption for whether or how to send authentication information identifying the application and its authorized users to the OAuth server.
FieldValue required
NameEnter any name to uniquely identify the record. For example, enter Guidewire OAuth2.0 API Credentials.
ActiveEnable
OAuth Entity ProfileSelect the OAuth profile you created when you registered the custom Equifax application as an OAuth provider. For example, select Equifax OAuth default profile.
Applies toSelect the MID Servers that can use this credential. For example, select All MID Servers.
OrderSelect the order to apply this credential. For example, enter 100.
  • Select Submit.

  • To generate the OAuth token, select the Get OAuth Token related link.

    Create Basic Auth credential record for the Guidewire spoke

    Create a Basic Auth credential record for the Guidewire application. The Guidewire connection and credential alias uses these credentials to authorize actions in Guidewire PolicyCenter, Guidewire ContactManager, and Guidewire ClaimCenter.

    Before you begin

    Role required: admin

    The following example shows the steps for creating a basic Auth credential record for Guidewire PolicyCenter, Guidewire ContactManager, and Guidewire ClaimCenter.

    Procedure

    1. Navigate to All > Connections & Credentials > Credentials.

    2. Select New.

      The system displays this message: What type of Credentials would you like to create?

    3. Select Basic Auth Credentials.

    4. On the form, fill in the fields.

      FieldDescription
      NameName to uniquely identify the record. For example, Guidewire.
      User nameUser name to be entered as credential.
      PasswordPassword to be entered as credential.
      ActiveOption to actively use the credential record. Select the option.
      OrderOrder that the credentials are used. For example, enter 100.
    5. Right-click the form header and select Submit.

    Switch between basic Auth and OAuth 2.0 credential

    You can choose to switch between implemented basic Auth and OAuth 2.0 authentication based on your event or security needs.

    Before you begin

    The following example shows the steps for switching from basic auth to OAuth 2.0 for the Guidewire ClaimCenter application.

    Procedure

    1. Navigate to AllConnections & CredentialsConnection & Credential Aliases.

    2. Select the Guidewire ClaimCenter record you want to re-configure.

    3. From the Connections tab, open the existing target connection record.

    4. In the Credential field, select the reference lookup icon.

    5. Select the credential record.

      • If switching the authentication method from basic auth to OAuth 2.0, select the credential record created during OAuth setup.
    6. If switching the authentication method from OAuth 2.0 to basic auth, select the credential record created during basic Auth setup.
    7. Save the record.

    What to do next

    Get Guidewire OAuth token

    Create connection record for the Guidewire spoke

    Create a connection record for your Guidewire application. The Guidewire connection and credential aliases use these connections to perform actions in Guidewire PolicyCenter, Guidewire ContactManager, and Guidewire ClaimCenter.

    Before you begin

    Role required: admin

    The following example shows the steps for creating a connection record for Guidewire PolicyCenter, Guidewire ContactManager, or Guidewire ClaimCenter.

    Procedure

    1. Navigate to All > Connections & Credentials > Connections & Credentials Aliases.

    2. Open the alias record, for example, Guidewire ClaimCenter.

    3. From the Connections tab, select New.

    4. On the form, fill these fields.

      FieldDescription
      NameName to uniquely identify the record. For example, Guidewire Connection.
      CredentialBasic Auth or OAuth 2.0 credential record created for Guidewire. For example, Guidewire OAuth2.0 API Credentials.
      Connection aliasAlias record associated with this connection.
      Connection URLBase URL to connect to Guidewire.
      ActiveOption to actively use the connection record.
      DomainDomain that the action runs in.
    5. Select Submit.

    Get Guidewire OAuth token

    Generate the Guidewire access token.

    Before you begin

    Role required: admin

    Procedure

    1. Navigate to All > Connections & Credentials > Credentials.

    2. Select the Guidewire spoke OAuth Credential record.

      For example, select Guidewire OAuth2.0 Credentials.

    3. From Related Links, select Get OAuth Token.

    Result

    The Guidewire spoke receives a new OAuth access token.

    sndocs is an independent community mirror and is not affiliated with or endorsed by ServiceNow.

    ServiceNow, the ServiceNow logo, Now, and other ServiceNow marks are trademarks and/or registered trademarks of ServiceNow, Inc., in the United States and/or other countries. Other company and product names may be trademarks of the respective companies with which they are associated.

    © 2026 ServiceNow, Inc. All rights reserved.

    Documentation content is redistributed under the Apache License 2.0 from the ServiceNowDocs repository.