Hendrik1

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-05-30
09:42
438 views
RSA Authentication Manager Provisioning
Hi
I have a request to integrate RSA Authentication Manager 8.4 with an existing NetIQ IDM 4.7 Environment.
Has anyone successfully achieved this using SOAP / Web Services / DB or anything else.
I prefer not procuring another Driver specifically for this such as the one from Trivir.
Any assistance will be appreciated.
Thanks
I have a request to integrate RSA Authentication Manager 8.4 with an existing NetIQ IDM 4.7 Environment.
Has anyone successfully achieved this using SOAP / Web Services / DB or anything else.
I prefer not procuring another Driver specifically for this such as the one from Trivir.
Any assistance will be appreciated.
Thanks
2 Replies


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-05-31
20:16
Hendrik;2500355 wrote:
Hi
I have a request to integrate RSA Authentication Manager 8.4 with an existing NetIQ IDM 4.7 Environment.
Has anyone successfully achieved this using SOAP / Web Services / DB or anything else.
I prefer not procuring another Driver specifically for this such as the one from Trivir.
Any assistance will be appreciated.
Thanks
Haven't done it. What APIs does it offer? Start there. If it's a SOAP or REST interface, it should be straightforward.


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-06-02
15:22
dgersic;2500399 wrote:
Haven't done it. What APIs does it offer? Start there. If it's a SOAP or REST interface, it should be straightforward.
Never tried on my own, but it looks like Authentication Manager from version 8.3 support REST API.
Authentication Manager 8.3+ or SecurID Access support a new REST based authentication API which will gradually replace the previous proprietary API that used a proprietary communication protocol on UDP port 5500 via SDKs available for selected platforms.
One of the big advantages of the new REST API is that it can be consumed from almost any platform capable of forming a valid REST request. The management of agent hosts is also simplified, as it doesn't require to establish a node secret.
The downside is that you'll have to take care of load balancing requests between your AM servers. Unlike the Authentication SDK, failover and load-balancing need to be taken care of by the consuming application or by infrastructure like a load balancer.
The REST API listens by default on TCP port 5555, although this can be changed to any other suitable port via the AM Security Console. On the same page you can enable the REST API.
http://safearea.com.au/blog/posts/2018/december/the-new-am-rest-authentication-api/