---
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


---

# Nonce process flow

# Nonce process flow {#ariaid-title1}

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

When a customer has implemented the digested token Single Sign-on and wishes to add the
security of a nonce, they follow a certain process flow.  
1. A user logs into the customer's portal.
2. The customer generates the required SSO parameters and appends a random nonce to the end. For example, if the customer were forwarding the authentication response via the query string, it may look something like this:

       SM_USER=itil&DE_USER=V1QuWMmxSfBgfRS099X0cAjKo5Q=&NONCE=1407743018

{#c_HighLevelOverview__ol_lwn_4hg_1p}

The instance receives this request and retrieves the authentication variables. Before
attempting to verify the integrity of the authentication response, the instance checks the nonce
against an internal table (u_authentication_nonce) to verify that it does not yet exist. If the
nonce does not exist within that table, the nonce is then added to the table and the
authentication process is allowed to continue. However, if that nonce value already exists within
the table, the authentication attempt is cancelled and an error code of
`failed_missing_requirement` is returned, which typically takes the user back to
the login page.