# Configure JIT on Identity Provider to update a dynamic value

**URL:** <https://devforum.okta.com/t/configure-jit-on-identity-provider-to-update-a-dynamic-value/30795>\
**Category:** SAML\
**Tags:** saml, idp\
**Created:** [October 2, 2024, 7:27am UTC](https://devforum.okta.com/t/configure-jit-on-identity-provider-to-update-a-dynamic-value/30795 "2024-10-02T07:27:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![manandan](https://avatars.discourse-cdn.com/v4/letter/m/779978/32.png) [@manandan](https://devforum.okta.com/u/manandan)\
**Post date:** [October 2, 2024, 7:27am UTC](https://devforum.okta.com/t/configure-jit-on-identity-provider-to-update-a-dynamic-value/30795/1 "2024-10-02T07:27:34Z")

</div>

Incoming SAML assertion contains an attribute that carries rather a dynamic value (UUID like) every time the user authenticates, JIT is able to store the incoming value into the user profile but only for the first time and never gets updated. Is there a way to force the update to happen?

I’m using the value into a custom claim in ID token and pass it on to the application, but the value it gets is not the latest one.

Any workaround for this?

Thanks, Mohan

---

<div class="post-metadata">

**Author:** ![andrea](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/andrea/32/2172_2.png) [@andrea](https://devforum.okta.com/u/andrea)\
**Post date:** [October 4, 2024, 4:26pm UTC](https://devforum.okta.com/t/configure-jit-on-identity-provider-to-update-a-dynamic-value/30795/2 "2024-10-04T16:26:47Z")

</div>

As you can see in the Mappings settings for an IdP, it is currently only possible to push attributes from the Identity Provider profile into the Okta User profile during user create, _unless_ the IdP in question is configured as a profile source  
Here are the mapping options when the IDP is not a Profile Source:

 ![Screenshot 2024-10-04 at 9.21.51 AM](https://global.discourse-cdn.com/oktadev/original/2X/a/ab8a464f9becb58b712db10aab0d281cfad2cad6.png)  
And here are the same options after I configure this IdP as a Profile Source:  
 ![Screenshot 2024-10-04 at 9.26.31 AM](https://global.discourse-cdn.com/oktadev/original/2X/3/3b873c0b74e352bb9e6d1598506c24d28fcc2488.png)

You can enable the Profile Source option when configuring the Identity Provider, as seen here:

 ![Screenshot 2024-10-04 at 9.25.37 AM](https://global.discourse-cdn.com/oktadev/original/2X/0/0bc91a3827568377a7fc8964be0b4e9f6480d6c7.png)

---

<div class="post-metadata">

**Author:** ![manandan](https://avatars.discourse-cdn.com/v4/letter/m/779978/32.png) [@manandan](https://devforum.okta.com/u/manandan)\
**Post date:** [October 7, 2024, 6:57am UTC](https://devforum.okta.com/t/configure-jit-on-identity-provider-to-update-a-dynamic-value/30795/3 "2024-10-07T06:57:46Z")

</div>

Thanks! That helps, on top of this, configured source priority on the profile mapping for the attribute as well.

 ![image](https://global.discourse-cdn.com/oktadev/original/2X/c/c2ccea35aa366fc5e78fe35baf4dc660105c0502.jpeg)

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/oktadev/original/1X/589c4c5f80de422d01f47cee7185a7fb8227835c.png) [@system](https://devforum.okta.com/u/system)\
**Post date:** [October 8, 2024, 6:58am UTC](https://devforum.okta.com/t/configure-jit-on-identity-provider-to-update-a-dynamic-value/30795/4 "2024-10-08T06:58:05Z")

</div>

Closed on October 8, 2024, 6:58am UTC

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.
