Federated Identity

This section contains guides for configuring Identity Providers (IdPs) to federate identity with Bentley's Identity Management System. Guides for all IdP's are not present, but we can federate with any IdP.

Overview:

• Federation Homepage
• CONNECTION Client configuration - domain hint, preferences, and options
• Verify how CONNECTED your users are
• Download the latest CONNECTION Client
• Check out what's new in IMS & User Management
• Frequently Asked Questions

Identity Provider Configuration:

• Setting up Azure AD OIDC Federation and the User Provisioning Sync Service
• Setting up OIDC over Okta
• Setting up OIDC with other Identity Providers

Deprecated - for review only:

• Setting up SAML 2.0 over Azure AD
• Setting up SAML 2.0 over ADFS
• Setting up SAML 2.0 with other Identity Providers
• Setting up OIDC over Azure AD

 Gathering a Network Trace (end result of all three is the same, there's just some noted differences between the apps): 

• Capturing a Fiddler Trace - Requires admin rights. Captures ALL network traffic on your machine during capture. Required for authentication related issues only existing inside the CONNECTION Client.
• Capturing a SAML Trace - Does not require admin rights, but you need to be able to install extensions in the browser. Only captures authentication related network information in this browser.
• Capturing a Browser-Based Trace - Does not require any install permissions.  Captures all network information in a specific tab or window, depending on your browser.