OAuth 2.0 authentication for LexisNexis
LexisNexis is withdrawing Basic Authentication from its Bridger Insight XG screening APIs by 31 December 2026. Fenergo SaaS now supports OAuth 2.0 client credentials, and each client moves its own connection across from the LexisNexis Credentials tab.
One credential set per tenant. The Client Id field takes the credential LexisNexis issues for OAuth 2.0 — a single value that acts as both the API key and the client ID — and a write-only Client Secret replaces Password. Once saved, the client secret is never displayed again.
Both methods run side by side. A client that has not switched keeps screening on Basic Authentication, and one client switching does not affect any other.
Nothing takes effect until Save & Test. The OAuth 2.0 toggle behaves like any other field on the tab. Selecting Save & Test saves the configuration and verifies it with LexisNexis, in either method, and the status chip reports the result.
Screening is unchanged. Same requests, same matching, same results. Access to the screen uses the permission that already governs Screening Provider configuration.
Client adoption
Request OAuth 2.0 credentials from LexisNexis, enter them on the Credentials tab, and select Save & Test. Allow time for LexisNexis to issue the credentials — that step is not immediate. If verification fails, screening does not run for the tenant until it is corrected.
Not included in this release
- Removal of the OAuth 2.0 toggle and the Basic Authentication fields, which stay until LexisNexis withdraws Basic Authentication.
- Any special handling for a tenant that has not switched when LexisNexis withdraws Basic Authentication.
- SFTP authentication for Ongoing Screening, which is unaffected.
- Rotating or expiring a client secret after the switch.
User Guide Reference: Configuring LexisNexis -> Authenticating with OAuth 2.0