IIQDisabled not working for JDBC Connector

[gmilunich (Geoff Milunich)]

I have a JDBC Connector, and am setting the value of “IIQDisabled” to true/false depending on another attribute as referenced in the documentation here: Loading a Single Account or Group

I also reviewed these two related articles:

Problem Disabling Accounts in JDBC Source

We have created a string field called IIQDisabled in the schema and added it in the SELECT statement as follows: SELECT * ,case when laboralState=‘ACTIVE’ then ‘false’ else ‘true’ end as IIQDisabled FROM database.table This is based on the documentation we found here: Loading Single Account Group in JDBC. The query works correctly when executed directly in the database. However, when performing the aggregation, the IIQDisabled field remains empty, and I fear this is why the relevant accounts a…

How to reflect enabled/disabled status of jdbc accounts?

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.

But neither helped.

When I look at the account, I can see the value is set correctly:

However, when I run the aggregation (unoptimized or through the UI) and the account status never changes, they are always Enabled.

What am I missing here? Is it Case-Sensitive? There are no rules attached to the source except JDBC Provisioning.

[sameertawargeri]

Can you try creating and attaching a JDBCBuildmap rule to the source, and add below line in the rule depending on your another attribute.
map.put(“IIQDisabled”, “true”);
Refer JDBC BuildMap Rule | SailPoint Developer Community

[gmilunich (Geoff Milunich)]

I should have mentioned I am trying to avoid that if possible, as it is one more thing to maintain when it should be possibly to pull it from the SQL, as described in the first link I mentioned. The value is showing correctly in the Account Attrbutes.

Side note: I believe I had this working before, but when I came back to this source to check something for certifications, it is no longer showing the enabled/disables status.

[mcheek (Mark Cheek)]

Are the conditions which IIQDisabled is set present in both the single and multiple account queries?

Unsure if it’s specifically required to be present in both, but was just curious

[patrickboston]

Try to wrap the IIQDisabled alias definition in the query in double quotes if it’s not already. This fixed it for me in one instance against an Oracle Database.

case when COL_NAME <> 'A' then 'true' else 'false' end as "IIQDisabled" 

[mcheek (Mark Cheek)]

Oddly enough at least for me it doesn’t seem to matter on SQL Server Databases

CASE
		WHEN u.IsActive = 0 THEN 'true'
		WHEN u.IsActive = 1 THEN 'false'
END AS IIQDisabled

[gmilunich (Geoff Milunich)]

@mcheek

Are the conditions which IIQDisabled is set present in both the single and multiple account queries?

Yes, this is what it looks like in the query:

@patrickboston

Try to wrap the IIQDisabled alias definition in the query in double quotes if it’s not already. This fixed it for me in one instance against an Oracle Database.

case when COL_NAME <> 'A' then 'true' else 'false' end as "IIQDisabled" 

I tried this as well, but noticed that it was not quoted on the one I am working with currently, so I an giving that a try now. I am working with an Oracle DB also in this instance.

[gmilunich (Geoff Milunich)]

@patrickboston

Try to wrap the IIQDisabled alias definition in the query in double quotes if it’s not already. This fixed it for me in one instance against an Oracle Database.

case when COL_NAME <> 'A' then 'true' else 'false' end as "IIQDisabled" 

It looks like this was it. I figured it had to be something simple. I did not have it quoted, which worked in the SQL Developer, but apparently not through ISC.

Side Note: When setting up the IIQDisabled value in the Schema, it did not care whether it was set to String or Boolean. Both worked once I got the query set.