Connect:Direct Java API supports certificate-based authentication. IBM Sterling Control Center also can use certificate-based authentication to connect and manage Connect:Direct settings. However latest version of RESTful API supports only user/password authentication. Please add certificate-based authentication for Connect:Direct RESTful API.
How will this idea be used?
Password/user authentication forces to use one of those solutions: common domain account (AD, LDAP, etc.) with password or maintain separate (e.g. local) users/passwords on each and every server with installed Connect:Direct. From security, compliance and operational standpoint both solutions are not ideal. RESTful API should support at least the same methods of authentication as other tools like Connect:Direct Java API or IBM Sterling Control Center.
|What is your industry?||Banking|
|What is the idea priority?||High|
|Link to original RFE|