# JDBC provisioning - two required attributes

**URL:** <https://developer.sailpoint.com/discuss/t/jdbc-provisioning-two-required-attributes/35811>\
**Category:** SHF Discussion and Questions\
**Tags:** provisioning, jdbc-connector, identity-security-cloud\
**Created:** [March 18, 2024, 2:04pm UTC](https://developer.sailpoint.com/discuss/t/jdbc-provisioning-two-required-attributes/35811 "2024-03-18T14:04:25Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![josephacciani](https://avatars.discourse-cdn.com/v4/letter/j/8c91f0/32.png) [@josephacciani](https://developer.sailpoint.com/discuss/u/josephacciani)\
**Post date:** [March 18, 2024, 2:04pm UTC](https://developer.sailpoint.com/discuss/t/jdbc-provisioning-two-required-attributes/35811/1 "2024-03-18T14:04:25Z")

</div>

I have a JDBC connector that, for provisioning, calls a stored procedure that was recently modified by the vendor to require two attributes. Is there a way to send both attributes through regardless if they are being synced?

---

<div class="post-metadata">

**Author:** ![coelhoya2](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/coelhoya2/32/8767_2.png) [@coelhoya2](https://developer.sailpoint.com/discuss/u/coelhoya2)\
**Post date:** [March 18, 2024, 3:20pm UTC](https://developer.sailpoint.com/discuss/t/jdbc-provisioning-two-required-attributes/35811/2 "2024-03-18T15:20:21Z")

</div>

@josephacciani Create a provisioning policy and map those attributes and in your provisioning rule you will send then.

---

<div class="post-metadata">

**Author:** ![iamnithesh](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/iamnithesh/32/4884_2.png) [@iamnithesh](https://developer.sailpoint.com/discuss/u/iamnithesh)\
**Post date:** [March 18, 2024, 3:24pm UTC](https://developer.sailpoint.com/discuss/t/jdbc-provisioning-two-required-attributes/35811/3 "2024-03-18T15:24:16Z")

</div>

Option 1: Add these attributes as plan arguments and read them in Connector rule  
Option 2: (little crooked) Add a new field in your query that will concatenate 2 attributes with a separator and assign it to the attribute that is marked as Account ID. Read this in Connector rule using `accountRequest.getNativeIdentity()` and then split using the separator

---

<div class="post-metadata">

**Author:** ![josephacciani](https://avatars.discourse-cdn.com/v4/letter/j/8c91f0/32.png) [@josephacciani](https://developer.sailpoint.com/discuss/u/josephacciani)\
**Post date:** [March 25, 2024, 10:29pm UTC](https://developer.sailpoint.com/discuss/t/jdbc-provisioning-two-required-attributes/35811/4 "2024-03-25T22:29:18Z")

</div>

I am attempting option 1 but am a bit new to this. I added the additional attributes to the Update policy for the source.

How do I read them into the Connector rule? I can’t seem to find what I am looking for in the documentation.

Thanks for the assist.

---

<div class="post-metadata">

**Author:** ![iamnithesh](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/iamnithesh/32/4884_2.png) [@iamnithesh](https://developer.sailpoint.com/discuss/u/iamnithesh)\
**Post date:** [March 26, 2024, 1:28pm UTC](https://developer.sailpoint.com/discuss/t/jdbc-provisioning-two-required-attributes/35811/5 "2024-03-26T13:28:16Z")

</div>

Option 1, I meant to say to be done using Before Provisioning Cloud rule

---

<div class="post-metadata">

**Author:** ![kdfreeman](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/kdfreeman/32/22737_2.png) [@kdfreeman](https://developer.sailpoint.com/discuss/u/kdfreeman)\
**Post date:** [March 26, 2024, 10:06pm UTC](https://developer.sailpoint.com/discuss/t/jdbc-provisioning-two-required-attributes/35811/6 "2024-03-26T22:06:03Z")

</div>

You can send that via creating provisioning policy in Source Account .  
Create a policy form via API that will pass the variables that you want. For example, you can pass ‘email’, ‘firstName’, ‘uid’ etc according to your requirements. Here is the API [create-provisioning-policy | SailPoint Developer Community](https://developer.sailpoint.com/docs/api/v3/create-provisioning-policy/)  
You can then get the value that you have passed in plan via following method. For example, if you want to fetch email that you have sent from plan:

`getAttributeRequestValue(account, "email")`

The function can be found in JDBC provisioning template provided by Sailpoint here. [JDBC Provision Rule | SailPoint Developer Community](https://developer.sailpoint.com/docs/extensibility/rules/connector-rules/jdbc-provisioning-rule/)

```auto
public String getAttributeRequestValue(AccountRequest acctReq, String attribute) {

    if ( acctReq != null ) {
      AttributeRequest attrReq = acctReq.getAttributeRequest(attribute);
      if ( attrReq != null ) {
        return attrReq.getValue();
      }
    }
    return null;
  }

```

Hope that helps.

---

<div class="post-metadata">

**Author:** ![josephacciani](https://avatars.discourse-cdn.com/v4/letter/j/8c91f0/32.png) [@josephacciani](https://developer.sailpoint.com/discuss/u/josephacciani)\
**Post date:** [March 27, 2024, 4:10pm UTC](https://developer.sailpoint.com/discuss/t/jdbc-provisioning-two-required-attributes/35811/7 "2024-03-27T16:10:52Z")

</div>

That all makes sense but I am struggling to get the attribute to be required even when it is not being updated during an attribute sync. The account name comes through fine as well as the attribute that needs to be updated but never the additional attribute that is required by the stored procedure.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [May 26, 2024, 4:11pm UTC](https://developer.sailpoint.com/discuss/t/jdbc-provisioning-two-required-attributes/35811/8 "2024-05-26T16:11:03Z")

</div>

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