<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
"400 Bad Request" Error when Connecting 3DEXPERIENCE Public SAAS with Okta
Single Sign-On
Okta Classic Engine
Okta Identity Engine
Overview

When attempting to log into the 3DEXPERIENCE Public SAAS platform, users might encounter a 400 Bad Request error. This issue generally arises when the platform is unable to accurately match user credentials, resulting in denied access to the system.

Applies To
 
  • 3DEXPERIENCE Public SAAS
  • Custom SAML 2.0
Cause

The error typically stems from a misconfiguration in the SAML attributes statement. If essential attributes like Country, Email, FirstName, LastName, and UserName are not appropriately defined or are missing, the user login process encounters a mismatch, leading to the "400 Bad Request" error.

Solution
  1. Reach out to the Service Provider (SP) Support to review the current configuration.
  2. Determine the requisite attributes needed for a successful login. These generally include: Country, Email, FirstName, LastName, and UserName.
  3. Update the Custom SAML Application attributes statement to accurately reflect these attributes.
  4. Conduct a system test to confirm that users are correctly matched and can successfully log in.
Loading
"400 Bad Request" Error when Connecting 3DEXPERIENCE Public SAAS with Okta