- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Collector via API
Hi,
I'm using RSA IGL 7.1 and I need to collect users and roles from Splunk.
The authentication in Splunk is done with LDAP (Active Directory) and we know that it exposes APIs in order to retrieve information about users and roles.
Is there a way to create an account data collector using "API" as Data Source Type?
Thank you,
Marta
- Tags:
- Collector
- Community Thread
- Data Collection
- Discussion
- Forum Thread
- Identity G&L
- Identity Governance & Lifecycle
- IG&L
- IGL
- RSA Identity
- RSA Identity G&L
- RSA Identity Governance & Lifecycle
- RSA Identity Governance and Lifecycle
- RSA IGL
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Be wary of any potential collector based on an API layer. Typically API's return data as an atomic transaction, one record at a time. These API's work great for connectors but tend to scale poorly for collectors where there may be large datasets to return. Even if a solution works logically, ensure that you can scale it to the size the data you plan on collecting.
Often it is simpler to use an API externally to aggregate the data to a flat file and then configure RSA Identity Governance & Lifecycle database collector to collect from the text file. The text driver is very simple but also gives the the flexibility to modify your queries easily if you need to.
RSA Professional Services can help you design these kinds of solutions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
At the moment, IG&L cannot connect to "custom" API to retrieve data. There are some prebuilt collectors for some applications using various APIs. There are SOAP and REST collectors in the roadmap for the near future. Q3-Q4 if I remember.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
REST Connector has been announced for Q1 2020 in the last webinar(last week).
So for moment, you have to dev your own script to create a file to collect it after.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Be wary of any potential collector based on an API layer. Typically API's return data as an atomic transaction, one record at a time. These API's work great for connectors but tend to scale poorly for collectors where there may be large datasets to return. Even if a solution works logically, ensure that you can scale it to the size the data you plan on collecting.
Often it is simpler to use an API externally to aggregate the data to a flat file and then configure RSA Identity Governance & Lifecycle database collector to collect from the text file. The text driver is very simple but also gives the the flexibility to modify your queries easily if you need to.
RSA Professional Services can help you design these kinds of solutions.
