This article explains how to resolve the following error that occurs when provisioning users from Okta to Rippling:

Status Code
400

{
"errorCode": "E0000001",
"errorSummary": "Api validation failed: gender",
"errorLink": "E0000001",
"errorCauses": [
{
"errorSummary": "gender: Value 'Male' for property 'gender' is not allowed for enum [male, female, nonbinary]"
}
]
}

• Attribute Mapping
• User Lifecycle Management
• Rippling Application

When provisioning a new user or updating an existing user's profile in Okta, the user fails to sync with the Rippling application.

The error is caused by a case-sensitivity mismatch between the value stored for the gender attribute in Okta and the value required by the Rippling API.

• The custom attributes may store gender values with a capital letter (for example, "Male," "Female").
• Rippling's API, however, has a strict validation rule requiring these values to be all lowercase (that is, "male", "female", "nonbinary").

When Okta attempts to provision the user, it sends the value from the user's profile (for example, "Male"). The Rippling API rejects this value and returns the validation error, causing the provisioning process to fail.

To resolve this issue, it is necessary to modify the attribute mapping in Okta to convert the gender value to lowercase before it is sent to Rippling.

1. Log in to the Okta Admin Console.
2. Navigate to Applications > Applications.
3. Select the Rippling application instance from the list.
4. Go to the Provisioning tab and then click on the To App section in the left-hand menu.
5. Click on the Attribute Mappings link.
6. Scroll down to the gender attribute mapping. The current mapping expression is likely something like user.gender.
7. Click the pencil icon next to the gender mapping to edit it.
8. In the expression field, replace the existing expression with the following Okta Expression Language (OEL) code:

   String.toLowerCase(user.gender)

NOTE: If the gender attribute is a custom attribute, replace user.gender with the correct variable name (for example, user.profile.custom_gender).

9. Click Save Mappings.
10. Click the Apply updates now button to immediately apply the changes.
11. After saving the new mapping, Okta will automatically convert the gender value to lowercase for all future provisioning events.

To confirm the issue is resolved:

1. Go to Dashboard > Tasks and click Retry Selected on the failed provisioning tasks. The tasks should now succeed.
2. For a new user, assign them to the Rippling application and verify that the provisioning process completes successfully without any errors in the Okta System Log.
3. Log in to Rippling and confirm that the user's gender field is now populated correctly with a lowercase value.

If the issue persists, please contact Rippling support for further assistance.