- Home
- Single Sign-On
- Datadog
Last updated: Nov 01, 2023
Overview
This Datadog app enables Single Sign-On and User Provisioning with SAML and SCIM.
The Challenge
As your internet facing identity platform, Okta is a source of valuable log data. Satisfying the Security, Operational and Regulatory requirements of your business requires powerful centralized logging and analytic capabilities.
- Stolen credentials are behind most data breaches and Security analysts need visibility into the right data at the right time to be able to quickly identify and triage credential-based attacks
- Authentication and provisioning issues can reduce end user productivity and administrators need proactively identify and quickly debug those issues
- Achieving and maintaining regulatory compliance can be time consuming and tedious
The Solution
With Datadog’s Okta log integration and log analytics, you can derive valuable insights from your Okta events. Enable the integration today to start monitoring Okta logs alongside the rest of your infrastructure. If you don’t already have a Datadog account, you can sign up for a free trial.
Once you’ve enabled the Okta integration in your Datadog account, you’ll be able to easily search, filter, and alert on all Okta events in Datadog.
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.
Okta Verified
The integration was either created by Okta or by Okta community users and then tested and verified by Okta.