IIQ WebService Connector - no auth with private_key_password

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Running on IIQ 8.4p2

We setup an app with the web service connector, specifying no authentication. The auth is handled by passing an x-api-key value in the header. The value for this key is just a string and there is no other auth, so we want to keep the value encrypted and not in plain text. To accomplish this, we set the header for each operation as: key=x-api-key, and value=$application.private_key_password$

Then in debug, we set the value: <entry key="private_key_password" value="apikey"/>

Once saved in debug, the api key is replaced with the encrypted value. This works perfectly fine, until a change is made to the application. Any change made through the application edit page, or even after a task completes and updates accounts, causes the private_key_password to disappear from the debug page and consequently any further operation on the app fails.

Is there a better way to store the x-api-key value to ensure it gets passed in the header on each operation, while staying encrypted? How can we ensure private_key_password doesn’t get wiped out?

Thanks

2

You can name your attributes anything you want. I’d avoid the out-of-box ones like private_key_password.

1 Like
3

Oh, if the issue is that you need the encrypted value, you can get that via a simple Beanshell rule that invokes “context.encrypt” on the string.

4

That seemed to do it. I made a new attribute x-api-key in debug, added it to the encrypted list, and it seems to stick now. Thanks!

2 Likes