JDBC Connector - Identity attribute [name] was not found error during Schema Preview

IdentityIQ (IIQ) IIQ Discussion and Questions
, ,
1

Hi Community,

image
image1722×785 34.1 KB

Screenshot 2026-04-28 180600
Screenshot 2026-04-28 1806001912×838 30.5 KB

I am configuring a PostgreSQL JDBC connector in SailPoint IdentityIQ 8.3
and getting the following error when clicking Preview on the Schema page:

Error: “Identity attribute [name] was not found.”

Setup Details:

  • Application Type: JDBC (PostgreSQL)
  • IIQ Version: 8.3
  • Schema Identity Attribute: name
  • Schema Display Attribute: name

SQL Statement:
SELECT r.rolname AS name,
r.rolcanlogin AS can_login,
r.rolvaliduntil AS expiry_date,
role.rolname AS granted_role
FROM pg_roles r
LEFT JOIN pg_auth_members mem ON mem.member = r.oid
LEFT JOIN pg_roles role ON mem.roleid = role.oid
WHERE r.rolcanlogin = true
ORDER BY r.rolname;

The Preview actually shows data correctly (name = q1007,
granted_role = demo_auditor) but still throws the error popup.

I have tried changing the Identity Attribute to uid, uname, and name
but all give the same “Identity attribute was not found” error.

Questions:

  1. What should the Identity Attribute field be set to in the Schema
    for a JDBC PostgreSQL connector?
  2. Does this field need to match an existing IIQ Identity attribute,
    or is it just the column name from the SQL result?
  3. Is this error blocking aggregation or just a Preview warning?

Any help appreciated. Thanks!

2

hi @Viraj

This is a known JDBC connector behavior.

About the Identity Attribute field:

  • It should be set to the unique account identifier column from your SQL result, not an IIQ Identity attribute.

  • In your case, name is correct since r.rolname AS name is unique and returned in the result set.

I would check below:

  1. Save the schema and reopen it before Preview
  2. Ensure the Identity Attribute exactly matches the column alias (name, case‑sensitive)
  3. Ignore the Preview error and run a test aggregation to confirm
3

Hey @Viraj ,

This is probably due to missing values for name from db end.please run the same query at db and make sure all the name fields filled with values

4

If not make sure all names are populated with values and then perform account aggregation

5

Performed all still same error.

6

@Viraj Can you run this query in the SQL tool and see the results. If there are any rows which doesn’t have the rolname column populated, it’ll throw the error. Could you please check and confirm. In case you have null values, please modify your query to exclude null users.

7

Have you performed the suggested steps?

8

Guys ThankYou for your support i found out in identity attribute one value was Null which was causing this error.

9

@Viraj Good to know that it is resolved. Whenever you get some time, could you please mark your post as resolved. This’ll help fellow sailor may having the similar issues.