I did some work recently setting up integration between IBM Security Secret Server and IBM Security Identity Intelligence and Intelligence (ISIGI) using the Adapter. This enables ISIGI to manage user accounts within Secret Server. In the process I made a few discoveries!

1. At the moment (November 2019) there is a problem which prevents running the Adapter in the Dispatcher within the ISIGI Virtual Appliance. This is due to be fixed at the end of 2019, but in the meantime it is necessary to run the Adapter in a separate Dispatcher.
2. In order for the integration to work it is necessary to enable web services in Secret Server. (I couldn’t find this mentioned in the adapter Installation and Configuration Guide or the Release Notes.)
3. If you are using a Secret Server username such as localadmin in the Secret Server Local domain, then in the driver configuration set ‘Secret Server User ID’ to localadmin.
4. If you are using a Secret Server username such as vharper in an Active Directory domain such as ‘Demo’, then in the driver configuration set ‘Secret Server User ID’ to demo\vharper.
5. This isn’t terribly surprising, but in the configuration the ‘Secret Server User ID’ is not case sensitive, whereas ‘Secret Server Password’ is case sensitive.

I hope that this is useful for someone out there!

Vaughan