Web Services in IIQ - Odd Test Connection Behavior

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Hi I hope you will able to read this I’m seeing a behavior in IdentityIQ where the Test Connection operation generates a new accesstoken if the current one is expired, but it does not update the persistent state (e.g., ExpiryTime and accessToken in the application XML). In contrast, operations such as Account Aggregation and Provisioning do update these values.

Is this by design—that Test Connection is treated as a “read-only” operation solely for verifying connectivity, without persisting changes? Any insights or references in the documentation that confirm this design intent would be greatly appreciated.

Thanks in advance

2

Hi Mia,

Thanks for your input. This appears to be related to using the product features. I’ve moved your comment to our IIQ Discussion and Questions category for greater help from the community.

Please refer to this page in our IIQ Connector Documentation for further reference: API Token Authentication

-Josh

1 Like