This article explains how to use the default value of a custom attribute when an application requires a default role. This is applicable when integrating with applications like LaunchDarkly, where a default role is required after Security Assertion Markup Language (SAML) provisioning.

Key aspects regarding the default custom attribute value:

• The default attribute value can only be selected for Okta User Type profiles.
• To use the default attribute value for a specific application, use profile mappings from Okta to the application.
• A default value can also be set for a custom attribute with no enumerated list of values.

• Okta UserType profiles
• Custom attributes with default values
• Lifecycle Management (LCM)

This could be a potential requirement from an application's side when a default Role is required when provisioning users, such as LaunchDarkly.

Please review the following article to understand the use case in greater detail: 

• LaunchDarkly SCIM Provisioning - The Role Assigned in the Okta Application Assignment Page is Not Reflecting Correctly on the LaunchDarkly Application Side

1. Create the attribute using an enumerated list of values. Ensure the attribute members contain a written value.

2. Select the default value from the dropdown menu.

3. Save the attribute.
4. Navigate to the application’s profile.
5. Create the role attribute.
6. Set the external namespace to urn:ietf:params:scim:schemas:extension:launchdarkly:2.0:User.
7. Navigate to the application’s mappings from Okta to LaunchDarkly.
8. Map the Okta custom attribute that contains the default value with the role attribute.