Overview

This KB article will guide the user through the process of fixing the issue of Jive not updating Profile Attribute via Okta sync.

Information

This section will provide valuable information about the environment in which this issue was observed.

Environment

• Jive Interactive Intranet version 2019.1
• SAML/SSO enabled with federated Attribute Mapping using Okta
• LDAP synced with Okta

Process

This section will guide the user through the process of reproducing the error, the expected and current behavior, and the resolution steps.

Reproduction Steps

1. In the LDAP user properties, modify the federated attributes which are synchronized through Okta.
2. Log in as the user whose attributes have been updated.
3. Go to user profile details and verify that the changes made in LDAP have been updated in Jive.

Expected Result

• LDAP attribute changes should sync with Okta, then sync with Jive upon login.
• The user's federated profile attributes should update.

Actual Result

One or more specific attributes are not updated.

Resolution

1. Check the exact case sensitive attribute name configured in Okta by requesting the SAML XML file from the user.
2. In the XML look for the code that starts with:
   <saml2:Attribute Name="YOUR_ATTRIBUTE_NAME"
Note the attribute name.

1. Go to the Jive Admin Console.
2. Click on People.
3. Click Settings.
4. Select the SAML tab.
5. Select the User Attribute Mapping sub-tab.
6. Scroll down to the name of the Attribute Mapping which is not syncing and verify that the spellings and case are the same as the attribute name found in step 2.
   

   Note:

   • The Okta document states the following about attribute names:
     The attribute names are case-sensitive while attribute operators are case-insensitive.
   • Attribute names are case sensitive, which means, hireDate is different from hiredate.
   • To know more about Okta API, refer to the Okta API Overview reading material.
7. If the attribute name doesn't match, select the attribute that needs to be changed and modify the Attribute Name to match the corresponding Okta attribute name listed in step 2.