- Home
- Zero Trust
- Beyond Identity
Last updated: Mar 29, 2021
Integration detail
Overview
Relying on a password to authenticate into your Okta applications puts your workforce’s accounts and company data at risk for account takeovers and data loss. It’s difficult to reduce the risk that occurs from insecure passwords, however, without adding significant user friction to the login experience
Passwordless authentication and risk-based access control for your desktop and single sign-on applications
The risks of passwords
Relying on a password to authenticate into your Okta applications puts your workforce’s accounts and company data at risk for account takeovers and data loss. It’s difficult to reduce the risk that occurs from insecure passwords, however, without adding significant user friction to the login experience.
How we authenticate users is changing
For the first time ever, your workforce can use proven, tested asymmetric keys and X.509 certificate-based authentication on every endpoint device without any key or certificate management, improving time to value and reducing IT workload. Unlike other friction-filled solutions, your workforce can self-enroll and download the Beyond Identity authenticator on every device to login to web-based and native applications without passwords, one-time codes, or needing to pick up a 2nd device every time they login. It’s a new type of authenticator that provides the device’s security posture at the exact time of login to make risk-based access decisions so only authorized users with devices that fit the company's risk policy can gain access.
Ease of passwordless integration and roll out
Beyond Identity’s passwordless identity platform is a cloud-native solution that can be easily integrated with Okta as a delegate identity provider (IDP). It requires only a few minor, code-free configuration changes in Okta. Beyond Identity employs standard OpenID Connect (OIDC) and SAML flows and SCIM for automated provisioning. Once provisioned, users can self enroll by downloading the authenticator and activating their credentials through email or their single sign-on end user portal.
How it works
When users request access to single sign on enabled applications, the application delegates to Okta and Okta subsequently delegates authentication responsibilities to Beyond Identity.
Functionality
Add this integration to enable authentication and provisioning capabilities.
Authentication (SSO)
-
API
-
Entitlement Management
-
Event Hooks
-
Inbound Federation
-
Inline Hooks
-
Outbound Federation
-
Partial Universal Logout
-
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.
-
Universal Logout
-
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.
-
More information about Okta + Beyond Identity
Read it
Okta Verified
The integration was either created by Okta or by Okta community users and then tested and verified by Okta.