# How to reflect enabled/disabled status of jdbc accounts? **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** identity-security-cloud, aggregation\ **Created:** [January 18, 2024, 2:34pm UTC](https://developer.sailpoint.com/discuss/t/how-to-reflect-enabled-disabled-status-of-jdbc-accounts/24449 "2024-01-18T14:34:26Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![jsosa](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/jsosa/32/31578_2.png) [@jsosa](https://developer.sailpoint.com/discuss/u/jsosa)\ **Post date:** [January 18, 2024, 2:34pm UTC](https://developer.sailpoint.com/discuss/t/how-to-reflect-enabled-disabled-status-of-jdbc-accounts/24449/1 "2024-01-18T14:34:26Z")
Hi! I have a JDBC connector, on which there is a table for users, with some status column. Value 1 means active, and value 2 inactive. How can I map these values to be reflected on IDN accounts screen? At aggregation data is brought right (disabled users appears with 2 status), but at the accounts screen level it remains as active. ---
**Author:** ![fmunerato](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/fmunerato/32/6029_2.png) [@fmunerato](https://developer.sailpoint.com/discuss/u/fmunerato)\ **Post date:** [January 18, 2024, 2:44pm UTC](https://developer.sailpoint.com/discuss/t/how-to-reflect-enabled-disabled-status-of-jdbc-accounts/24449/2 "2024-01-18T14:44:47Z")
Hi Julian, I don’t know if the JDBC will behave the same way as the WebService connectors, but on the WebService Connector we use de attribute IIQDisabled attribute mapped to the account. This attribute defines the status of the account on IDN Screen. This attribute it’s only true or false, so maybe you will have to create some data transformation using Rules or something. Here it’s an article regarding this attribute using the WebService connector, maybe you can find some more information there _[Generic after rule for account status in webservice source](https://developer.sailpoint.com/discuss/t/generic-after-rule-for-account-status-in-webservice-source/4058)_ ---
**Author:** ![jsosa](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/jsosa/32/31578_2.png) [@jsosa](https://developer.sailpoint.com/discuss/u/jsosa)\ **Post date:** [January 18, 2024, 2:51pm UTC](https://developer.sailpoint.com/discuss/t/how-to-reflect-enabled-disabled-status-of-jdbc-accounts/24449/3 "2024-01-18T14:51:16Z")
> [@fmunerato](#): > > t’s an article Hi Felipe! That should mean to add it to the account schema? I will try it, as using a sql select, I think I can do it as simple as a case around the status field, and aliasing the field to IIQDisable name. ---
**Author:** ![jsosa](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/jsosa/32/31578_2.png) [@jsosa](https://developer.sailpoint.com/discuss/u/jsosa)\ **Post date:** [January 18, 2024, 3:19pm UTC](https://developer.sailpoint.com/discuss/t/how-to-reflect-enabled-disabled-status-of-jdbc-accounts/24449/4 "2024-01-18T15:19:51Z")
Hi Felipe! Just tested it, but unfortunately it does not work for this connector. I add it to schema: ![image](https://global.discourse-cdn.com/sailpoint/original/2X/3/32babe7b6c7a99c4cd2ce882996e86b2d78614e1.png) and to the query: ![image](https://global.discourse-cdn.com/sailpoint/original/2X/b/bd794fd36c3cd86c60cf7d480a9ceeb300cf20b9.png) ---
**Author:** ![fmunerato](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/fmunerato/32/6029_2.png) [@fmunerato](https://developer.sailpoint.com/discuss/u/fmunerato)\ **Post date:** [January 18, 2024, 4:17pm UTC](https://developer.sailpoint.com/discuss/t/how-to-reflect-enabled-disabled-status-of-jdbc-accounts/24449/5 "2024-01-18T16:17:33Z")
Hi Julian, I don’t know if it will make any difference, but you try to set the attribute type as boolean on the schema? ---
**Author:** ![baoussounda](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/baoussounda/32/13095_2.png) [@baoussounda](https://developer.sailpoint.com/discuss/u/baoussounda)\ **Post date:** [January 18, 2024, 8:48pm UTC](https://developer.sailpoint.com/discuss/t/how-to-reflect-enabled-disabled-status-of-jdbc-accounts/24449/6 "2024-01-18T20:48:26Z")
> [@jsosa](#): > > add it to schema Hi, You can use JDBC builMap rule to override your attribute status value. [https://developer.sailpoint.com/idn/docs/rules/connector-rules/jdbc-buildmap-rule](https://developer.sailpoint.com/idn/docs/rules/connector-rules/jdbc-buildmap-rule) ---
**Author:** ![jsosa](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/jsosa/32/31578_2.png) [@jsosa](https://developer.sailpoint.com/discuss/u/jsosa)\ **Post date:** [January 19, 2024, 12:07pm UTC](https://developer.sailpoint.com/discuss/t/how-to-reflect-enabled-disabled-status-of-jdbc-accounts/24449/7 "2024-01-19T12:07:13Z")
This “status” field column is mapped directly to account status, or it has to be added in schema? ---
**Author:** ![baoussounda](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/baoussounda/32/13095_2.png) [@baoussounda](https://developer.sailpoint.com/discuss/u/baoussounda)\ **Post date:** [January 19, 2024, 12:08pm UTC](https://developer.sailpoint.com/discuss/t/how-to-reflect-enabled-disabled-status-of-jdbc-accounts/24449/8 "2024-01-19T12:08:44Z")
This status is example, you can replace it with your source status attribute present in you source schemas ---
**Author:** ![jsosa](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/jsosa/32/31578_2.png) [@jsosa](https://developer.sailpoint.com/discuss/u/jsosa)\ **Post date:** [January 19, 2024, 5:26pm UTC](https://developer.sailpoint.com/discuss/t/how-to-reflect-enabled-disabled-status-of-jdbc-accounts/24449/9 "2024-01-19T17:26:40Z")
Hi Ousmane, I think the attribute value is not problematic here, because I can brought it with expected value in the query itself (via the SELECT CASE statement, for example … CASE status WHEN 1 then ‘false’ ELSE ‘true’ END AS IIQDisabled ---
**Author:** ![jsosa](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/jsosa/32/31578_2.png) [@jsosa](https://developer.sailpoint.com/discuss/u/jsosa)\ **Post date:** [January 19, 2024, 5:42pm UTC](https://developer.sailpoint.com/discuss/t/how-to-reflect-enabled-disabled-status-of-jdbc-accounts/24449/10 "2024-01-19T17:42:50Z")
Hi Felipe, tried IIQDisabled as boolean, but nothing changes. I think the IIQDisabled fake attribute is used on AD in provisioning only, is not present on the AD schema also. I raised a support request, so if they can guide me I will return with the answer. ---
**Author:** ![baoussounda](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/baoussounda/32/13095_2.png) [@baoussounda](https://developer.sailpoint.com/discuss/u/baoussounda)\ **Post date:** [January 19, 2024, 7:45pm UTC](https://developer.sailpoint.com/discuss/t/how-to-reflect-enabled-disabled-status-of-jdbc-accounts/24449/11 "2024-01-19T19:45:51Z")
> [@jsosa](#): > > itself Hi @jsosa , Do you try to add `IIQDisabled` in source schemas ? I see this : ![image](https://global.discourse-cdn.com/sailpoint/original/2X/a/abbaf54e0e4d34c20e286c06581a9096894f3e2d.png) [Loading a Single Account or Group (sailpoint.com)](https://documentation.sailpoint.com/connectors/jdbc/help/integrating_jdbc/loading_single_account_group.html) ---
**Author:** ![jsosa](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/jsosa/32/31578_2.png) [@jsosa](https://developer.sailpoint.com/discuss/u/jsosa)\ **Post date:** [January 19, 2024, 8:03pm UTC](https://developer.sailpoint.com/discuss/t/how-to-reflect-enabled-disabled-status-of-jdbc-accounts/24449/12 "2024-01-19T20:03:04Z")
Hi Ousmane! Yes I have tested it, but account still appears as Enabled. I got this message from support, they say that this feature is not ready yet, so I think it only remains to wait: ![image](https://global.discourse-cdn.com/sailpoint/original/2X/d/d4abaf2759bc3d51dc778cdf94579fe53b819a38.png) But when implemented for sure will be using this IIQDisabled attribute. Thanks everyone! ---
**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:** [February 2, 2024, 6:48pm UTC](https://developer.sailpoint.com/discuss/t/how-to-reflect-enabled-disabled-status-of-jdbc-accounts/24449/13 "2024-02-02T18:48:49Z")
Hi Julian, Actually it’s possible and i have configured in my Tenant. ```auto **** , case when IIQDisabled="True" then 'true' else 'false' end as "IIQDisabled" from authoritative_source .... ``` In my case we have a attribute called IIDisabled in our database that can be “true” or “false” as string, but you can do with any other attribute. ![image](https://global.discourse-cdn.com/sailpoint/original/2X/1/1e29612447b103cb56e6a0544c8ebf986e38bdb3.png) I have also mapped in Account Schema but I’m not so sure if it’s necessary. Based in your print screen your query should be: case when ATTRIBUTE=1 then ‘false’ else ‘true’ end as IIQDisabled Please let me know if works for you. ---
**Author:** ![jsosa](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/jsosa/32/31578_2.png) [@jsosa](https://developer.sailpoint.com/discuss/u/jsosa)\ **Post date:** [February 4, 2024, 5:59pm UTC](https://developer.sailpoint.com/discuss/t/how-to-reflect-enabled-disabled-status-of-jdbc-accounts/24449/14 "2024-02-04T17:59:07Z")
Thanks Yan, working! true/false order was incorrect. ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [April 4, 2024, 6:00pm UTC](https://developer.sailpoint.com/discuss/t/how-to-reflect-enabled-disabled-status-of-jdbc-accounts/24449/15 "2024-04-04T18:00:01Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.