---
sourceDocument: Brazil Public Sector
sourceDocumentLink: https://www.servicenow.com/docs/r/government-industry

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Public Sector

ft:clusterId :

    - gvin

bundleId :

    - gvin

workflow :

    - Customer and Industry


---

# Identity Provider Integration

# Identity Provider Integration plugin {#ariaid-title1}

Release version: Brazil  
Updated October 1, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
The Identity Provider Integration plugin (sn_idp_integ) allows provides ServiceNow developers with the data model foundation to develop OpenID Connect (OIDC) integrations that authenticate and verify constituent identities
through approved government OpenID Connect (OIDC) providers --- ID.me (US), myID (Australia), GOV.UK One Login (UK) --- replacing email-only identification. It standardizes and enhances the identity verification process, delivering a
provider-neutral OIDC framework for capturing and storing key identity provider data, including identity provider issuer, identity provider ID, and assurance level from OIDC providers on top of the existing Multi-Provider SSO (MPSSO)
plugin.
Identity Provider Integration adds a new standalone table that stores OIDC identity-provider metadata for externally authenticated users. The table supports more than one identity-provider association per user over time. This
enables agencies to reliably identify constituents, prevent duplicate accounts, and protect sensitive data via role-based ACLs. The model supports multiple providers per user, and enforces provenance-based write access to downstream
user fields.  
Two MPSSO configurations support the workflow:

* Login Authentication Configuration --- the standard "Sign in with ID.me" login flow, configured with scopes that only require self-reported user attributes,
* Verification configuration--- the "Verify with ID.me" step-up flow, configured with scopes that require remotely verified user attributes
{#psds-identity-framework-landing__ul_bfv_4l3_tkc}

Both Provider configurations return OIDC claims through the same MPSSO transform script, validated against the OIDC provider sandbox. The script, which runs a find-or-create logic before a new user is created from an OIDC provider
login, checks if this identity already exists by searching the `sn_idp_integration` table for a Identity Provider Issuer + Identity Provider ID match, reusing the existing, verified user instead of creating a
duplicate if it finds a match, or creating a new user record table entry if there's no match.
For more information about the Identity Provider Integration plugin, see [Identity Provider Integration Data Model](https://www.servicenow.com/docs/9VY2IyVAxP3PYXWC6ir8aQ "The Identity Provider Integration (sn_idp_integ) plugin provides ServiceNow developers the data model foundation to develop OpenID Connect (OIDC) integrations to authenticate and verify constituent identities through approved government OIDC providers — ID.me (US), myID (Australia), GOV.UK One Login (UK) — replacing email-only identification. The Identity Provider Integration standardizes and enhances the identity verification process, delivering a provider-neutral OIDC framework for capturing and storing identity provider data, including identity provider issuer, identity provider ID, and assurance level from OIDC providers.").
**Related tasks**   

* [Install Identity Provider Integration](https://www.servicenow.com/docs/Dq_K9UnmsP784v8TtoV3gw "You can install the Identity Provider Integration plugin (sn_idp_integ) if you have the admin role.The application includes demo data and installs related ServiceNow Store applications and plug-ins if they aren’t already installed.")