---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Configure a custom authentication algorithm

# Configure a custom authentication algorithm {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Generate the custom data needed to authenticate to a web service by running
script.

## Vorbereitungen

* JavaScript knowledge
* REST knowledge
* Target web service API knowledge
* Connection, credential, and alias knowledge
* Role required: Developer
{#configure-a-custom-authentication-algorithm__ul_ybf_vcf_wrb}

## Warum und wann dieser Vorgang ausgeführt wird

Use a connection and credential alias and custom authentication based algorithm for
authentication.

## Prozedur

1. Navigate to AllCredentials \& ConnectionsAuthentication Algorithms, and click New.
2. On the form, fill in the fields.  
   The database selection in the Format field determines which fields are available.  
   {#configure-a-custom-authentication-algorithm__table_dls_tpv_sx__entry__2}

   | Field | Description |
   |-|-|
   | Name | Unique name of this algorithm. |
   | Algorithm | Outbound request type. Select Custom Authentication. |
   | Description | Description of what your algorithm does. |
   | Application | Scope that your application runs in. |
   | Instance Authentication Script | Script that you select from the Script Includes table. The scripts available are as follows: * RequestAuthAWSV4Signer * RequestAuthInternal * RequestAuthSampleCustomSigner * RequestAuthTwitterSigner {#configure-a-custom-authentication-algorithm__ul_crt_tvl_rsb} Hinweis: * To know more about the script click the information icon next to the field. The details of the script such as Name, API Name, Application, Accessible from, Script, and so on is displayed. * In case of custom authentication with Twitter, you can choose RequestAuthTwitterSigner, since it uses an OAuth 1.0a method of authentication. This requires informations such as API key and secret and Access token and secret that can be used to create signatures to pass in an authorization header. For more information, see [Authentication in Twitter](https://developer.twitter.com/en/docs/authentication/oauth-1-0a). {#configure-a-custom-authentication-algorithm__ul_j5p_vz4_ssb} |
   | MID Authentication Script | Script that you select from the MID Server Script Includes \[Discovery view\] table. The scripts available are as follows: * RequestAuthAWSV4Signer * RequestAuthInternal * RequestAuthSampleCustomSigner * RequestAuthTwitterSigner {#configure-a-custom-authentication-algorithm__ul_ugg_lcp_ssb} |
   [Tabelle : 1. Authentication form]

   {#configure-a-custom-authentication-algorithm__table_dls_tpv_sx}

   Based on the selected scripts and authentication algorithm, the
   configured credentials is sent as outbound request from ServiceNow to the provider.
3. Click Update.
4. Navigate to AllConnections \& CredentialsCredentials.
5. Click New.
6. Create Twitter Credentials with Authentication Algorithm.  
   In this case TwitterAuthAlgo.
7. Specify the fields:  
   * Name
   * Active
   * Access token
   * Access token secret
   * Consumer key
   * Consumer secret
   * Credential alias
   * Authentication Algorithm

   {#configure-a-custom-authentication-algorithm__ul_c2t_qvy_1tb}
8. Click Update.
{#configure-a-custom-authentication-algorithm__steps_cdq_dpy_qsb}

## REST step with Twitter {#configure-a-custom-authentication-algorithm__example_jpk_lyl_rsb}

In case of Twitter, you must ensure the following spokes or credentials are available:

* Access token
* Access token secret
* Consumer key
* Consumer secret
* Authentication Algorithm

{#configure-a-custom-authentication-algorithm__ul_tzw_pbp_ssb}

Action: TwitterAuthAlgo.  
Input REST step with Twitter as follows:

* Credentials Alias: The alias that is created for Twitter.
* Base URL: Base URL details from Twitter.
* HTTPS Method: In this case it is POST method. Posting a tweet.
* Query Parameters: Action as tweet.
{#configure-a-custom-authentication-algorithm__ul_ojh_z54_ssb}

You can test the action. The tweet is posted on the Twitter page.