- Home
- Single Sign-On
- PerimeterX
Overview
Stop automated bot attacks on your web and mobile applications. PerimeterX Bot Defender integrates with the Okta Risk Ecosystem API to help stop automated attacks on websites. With this integration, Okta can consume rich risk data in realtime from Bot Defender and prevent credential stuffing and account takeover attacks.
The Challenge
Your customers reuse passwords across multiple accounts and apps.
With over 15 billion compromised credentials out in the wild, bots are constantly targeting your login pages.
Successful account takeover attacks results in fraudulent transactions and PII exposure, increasing costs for your business.
The Solution
PerimeterX integrates with Okta to eliminate bots from your authentication and account registration flows.
Okta ingests risk signals from PerimeterX Bot Defender to further enhance bot detection and reduce the risk of account takeover attacks. The cloud-native Bot Defender combines intelligent fingerprinting, behavioral signals and predictive analysis to detect bots and report them using the Okta Risk Engine API.
The DevOps-friendly integration deploys easily through the Okta sign-in page and can be operational within minutes.
Benefits
- Stop automated bot attacks without impacting customer experience
- Enforce enhanced security policies by leveraging rich risk data from Bot Defender
- Reduce fraud by preventing credential stuffing, account takeover and fake account creation
Functionality
Add this integration to enable authentication and provisioning capabilities.
Authentication (SSO)
-
API
-
Event Hooks
-
Inbound Federation
-
Inline Hooks
-
Outbound Federation
-
RADIUS
-
SAML
Security Assertion Markup Language is an open standard for exchanging authentication and authorization data between an identity provider (IdP) and a service provider (SP) that does not require credentials to be passed to the service provider.
-
Workflow Templates
-
Workflows Connectors
-
SWA
Secure Web Authentication is a Single Sign On (SSO) system developed by Okta to provide SSO for apps that don't support proprietary federated sign-on methods, SAML or OIDC.
-
OIDC
OpenID Connect is an extension to the OAuth standard that provides for exchanging Authentication data between an identity provider (IdP) and a service provider (SP) and does not require credentials to be passed from the Identity Provider to the application.
-
WS-Federation
Provisioning
-
Create
Creates or links a user in the application when assigning the app to a user in Okta.
-
Update
Okta updates a user's attributes in the app when the app is assigned. Future attribute changes made to the Okta user profile will automatically overwrite the corresponding attribute value in the app.
-
Attribute Sourcing
The application can be defined as the source of truth for a full user profile or as the source of truth for specific attributes on a user profile.
-
Deactivate
Deactivates a user's account in the app when it is unassigned in Okta or their Okta account is deactivated. Accounts can be reactivated if the app is reassigned to a user in Okta.
-
Sync Password
Push either the users Okta password or a randomly generated password to the app. This feature is not required for all federated applications as user authentication takes place in Okta, however some apps still require a password.
-
Group Push
Push existing Okta groups and their memberships to the application. Groups can then be managed in Okta and changes are reflected in the application.
-
Group Linking
Link Okta groups to existing groups in the application. Simplifies onboarding an app for Okta provisioning where the app already has groups configured.
-
Schema Discovery
Import the user attribute schema from the application and reflect it in the Okta app user profile. Allows Okta to use custom attributes you have configured in the application that were not included in the basic app schema.
-
Attribute Writeback
When the application is used as a profile master it is possible to define specific attributes to be sourced from another location and written back to the app. For example the user profile may come from Active Directory with phone number sourced from another app and written back to Active Directory.
Documentation
Here is a section all about documentation, integration, and implementation.
-
Webpage:
Okta + PerimeterX Partnership Overview
Read it
