{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":21449,"path":"integrate-applications/integration-hub/set-up-verifi-spoke.md","title":"Set up Verifi Spoke","bundle":null,"doc_type":null,"release":"australia","body":"\n# Set up Verifi Spoke\n\nIntegrate the ServiceNow instance and Verifi account by using the JWT authentication to authenticate ServiceNow requests.\n\n## Before you begin\n\n-   Request an Integration Hub subscription.\n-   Activate the Verifi spoke.\n-   Role required: admin.\n\n## About this task\n\nJSON Web Tokens \\(JWTs\\) enable the capability to configure server-to-server API interactions between ServiceNow and external API providers without requiring any user intervention.\n\n## Procedure\n\n1.  Generate a JSON Web Token \\(JWT\\).\n\n    Create a JWT for your instance by using this link to enable JWT authentication. For Verifi Spoke, generate the authorization by using the *VerifiAuthorizationTokenGenerator* script. For more information, see [Generate a JSON Web Token \\(JWT\\)](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/Scoped-API-generate-JWT.md).\n\n2.  Create credential records for the Verifi Spoke.\n\n    Create a connection and credential record for the Verifi Spoke application. The Verifi Spoke connection and credential alias uses these credentials to authorize actions. For more information, see [Create a connection and a credential record for the Verifi Spoke](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/integration-hub/set-up-verifi-spoke.md).\n\n\n## Create a connection and a credential record for the Verifi Spoke\n\nCreate a connection and credential record for the Verifi Spoke application. The Verifi Spoke connection and credential alias uses these credentials to authorize actions.\n\n### Before you begin\n\n-   A shared secret for signing the authentication token.\n-   Create a JSON Web Token \\(JWT\\) key. Associate a JWT provider with the signing configuration by referring to a JWT key.\n-   An Issuer ID assigned by Verifi. The ID is included in the request headers and authentication token to identify the issuer making API calls.\n-   Role required: admin\n\n### Procedure\n\n1.  Navigate to **All** > **Connections & Credentials** > **Connection & Credential Aliases**.\n\n2.  Select the **Verifi** record.\n\n    The Connection & Credential Aliases page opens.\n\n3.  On the form, fill in the fields.\n\n    |Field|Description|\n    |-----|-----------|\n    |Name|Name of the alias. An alias can only contain the alpha, number, and underscore characters.|\n    |ID|Unique identifier for the Connections & Credentials alias, based on the format `sn_verifi_spoke.Verifi`.|\n    |Application|Application scope against which the Connection & Credentials alias is assigned. The current session scope that you last selected in the application picker appears. For example, **Verifi Spoke** appears if it is the current scope for this session.|\n    |Type|Alias type. Select **Connection and Credential**.|\n    |Connection type|Name of the connection type, either Basic, HTTP, JDBC, JMS, or Kafka. The default is HTTP.|\n    |Support Multiple Active Connections|Designator that indicates whether the alias supports multiple active connections. Add connections by using the Connections table and associate them to the alias by using the Connections related list.|\n    |Default Retry Policy|Retry policy for the alias. For more information, see [Retry policy](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/retry-policy.md).|\n    |Configuration Template|Configuration template to use to create a connection and credential record.|\n\n4.  Select **Save**.\n\n    The Connections and Connection Attributes related list appears.\n\n    |Related List|Description|\n    |------------|-----------|\n    |Connections|Related connection records associated with this alias. After creating the alias, you can define the connection records and associate them with the alias. If **Support Multiple Active Connections** is selected, you can associate more than one connection with an alias.|\n    |Connection Attributes|Attributes for the connection. Define the data that is specific to a connection and use it in an Integration Hub integration step.|\n    |Child Aliases|Child aliases that are associated with the parent alias. After creating a connection and credential alias, you can create a child alias to configure multiple connections for the same application integration.|\n\n5.  If you want to create a new credential and connection associated with your credential alias, under **Related Links**, select **Create New Connection & Credential**.\n\n    In the dialog box, fill in the fields.\n\n    |Field|Description|\n    |-----|-----------|\n    |Please Enter the Connection Information|\n    |Connection Name|Name of the connection.|\n    |Connection URL|URL used for connecting to the server on which Verifi Spoke is installed.|\n    |Issuer|An Issuer ID that you copied while setting up the Verifi Spoke by using the JWT authentication type.|\n    |API Version|API version that the related spokes are built for. The default value is `4.0`.|\n    |JWT Provider|JWT Provider that you provided while setting up the Verifi Spoke spoke by using the PAT authentication type.|\n\n6.  If you want to create a child alias for your connection and credential alias, under the Child Aliases related list, select **New**.\n\n    1.  Enter a name for the child alias and select **Submit**.\n\n        The child alias inherits the properties from the parent alias. You can then configure a child alias to contain its own set of connection and credential information.\n\n\n### Result\n\nA connection and credential record is created in the ServiceNow instance.\n\n"}}