Hello Team,
We are at ISAM 9.0.7.1 IF 5 and using externalized config database. While creating Client definition, LMI log throws below error.

6/15/20 14:35:32:635 EDT] 000a95de m.security.access.managed.resources.impl.ManagedResourceImpl I com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException: One or more values in the INSERT statement, UPDATE statement, or foreign key update caused by a DELETE statement are not valid because the primary key, unique constraint or unique index identified by "1" constrains table "DB2INST3.FIM_MAPPING_RULES" from having duplicate values for the index key.. SQLCODE=-803, SQLSTATE=23505, DRIVER=4.23.42

Any suggestion will be helpful.

Thanks,
Bipin


------------------------------
Bipin Dash
------------------------------

Hey Bipin,

Could I find out the steps to recreate the issue? This error is usually thrown when a mapping rule with Definition name+"PreTokenGeneration" or Definition name + "PostTokenGeneration" already exists prior to creating Definition.

Thanks,

------------------------------
Geethanjali D
------------------------------

Original Message:
Sent: Mon June 15, 2020 03:06 PM
From: Bipin Dash
Subject: ISAM 9.0.7.1 IF 5 - Issue while creating OAuth/OIDC definition

Hello Team,
We are at ISAM 9.0.7.1 IF 5 and using externalized config database. While creating Client definition, LMI log throws below error.

6/15/20 14:35:32:635 EDT] 000a95de m.security.access.managed.resources.impl.ManagedResourceImpl I com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException: One or more values in the INSERT statement, UPDATE statement, or foreign key update caused by a DELETE statement are not valid because the primary key, unique constraint or unique index identified by "1" constrains table "DB2INST3.FIM_MAPPING_RULES" from having duplicate values for the index key.. SQLCODE=-803, SQLSTATE=23505, DRIVER=4.23.42

Any suggestion will be helpful.

Thanks,
Bipin


------------------------------
Bipin Dash
------------------------------

Hi Geethanjali,

Thanks for responding. I was able to fix the issue.
Root cause:
Previously config db was local within appliance and issue started when we did externalization. By looking at data in FIM_MAPPING_RULE - rule_id (primary key) had values from 0 to 121 sequentially and then it's 124. I believe when we create ISAM definition, it tries to insert data with same rule_id 124.

Resolution steps:

1. updated the rule_id to 122 to make it in sequence after 121
2. updated the reference rule id from 124 to 122 in feds.xml in table fim_default_configs

Please give your suggestion.

Thanks,
Bipin

------------------------------
Bipin Dash
------------------------------

Original Message:
Sent: Wed June 17, 2020 07:00 AM
From: Geethanjali D
Subject: ISAM 9.0.7.1 IF 5 - Issue while creating OAuth/OIDC definition

Hey Bipin,

Could I find out the steps to recreate the issue? This error is usually thrown when a mapping rule with Definition name+"PreTokenGeneration" or Definition name + "PostTokenGeneration" already exists prior to creating Definition.

Thanks,

------------------------------
Geethanjali D

Original Message:
Sent: Mon June 15, 2020 03:06 PM
From: Bipin Dash
Subject: ISAM 9.0.7.1 IF 5 - Issue while creating OAuth/OIDC definition

Hello Team,
We are at ISAM 9.0.7.1 IF 5 and using externalized config database. While creating Client definition, LMI log throws below error.

6/15/20 14:35:32:635 EDT] 000a95de m.security.access.managed.resources.impl.ManagedResourceImpl I com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException: One or more values in the INSERT statement, UPDATE statement, or foreign key update caused by a DELETE statement are not valid because the primary key, unique constraint or unique index identified by "1" constrains table "DB2INST3.FIM_MAPPING_RULES" from having duplicate values for the index key.. SQLCODE=-803, SQLSTATE=23505, DRIVER=4.23.42

Any suggestion will be helpful.

Thanks,
Bipin


------------------------------
Bipin Dash
------------------------------