Suggestions for connector selection

Which IIQ version are you inquiring about?

8.3p3

Share all details about your problem, including any error messages you may have received.

We have a requirement to create different logical applications based on certain AD groups membership(identified using naming convention pattern or hardcoded names of the ad groups). Eg. If User A’s AD account is a member of any of the Group A1, A2,A3 then he should have Application A. We want to have some segregation / grouping of people that will allow us to have better governance which will in turn allow us to manage certifications using these new apps so that the respective certifiers can take the action and the provisioning should be triggered on the actual AD application. Also these applications will also help with reports and dashboards.

I’m currently going through the Logical, Multiplex and Logiplex connector documents to understand which would fit better for these requirements.

Any suggestions are welcome.

Hi @AroraA3 , Logiplex is recommended to handle this kind of requirement . You can go through below link -

https://community.sailpoint.com/t5/Professional-Services/PSLabs-LogiPlex-Connector/ta-p/172304

Feel free to reach out in case you need any help . Thanks.

Couple of benefits of Using Logiplex over Logical -

  1. As per my understanding Logical don’t support SOD .

  2. Logical don’t support Native change detection as well . and there are other pros and cons which you can explore .

Hi Harsh,

Thanks for your response, I’m going through the document, the question i have is would using the Adaptor mode in the Logiplex make sense or the classic?

Hi @AroraA3 ,

Its up to you , but i would say Adaptor Mode . You won’t have to onboard one more application to drive the functionality . Just put couple of rules and you are all set .

Hi @harsh_gupta4 okay sure, thanks.

I tried configuring in Adaptor mode, the application was generated, however, the new sub application generated did not have any accounts as such, how do i make it show accounts? Also i noticed that the sub application did not have any configuration details, ou details, schema attributes etc. What all do i need to copy for my requirements?

Bumping this thread.

Hi @menno_pieters - I have been trying to use Logiplex in Adapter mode for AD application.

I’ve updated the AD application connector class to logiplex and add the masterconnector and the split rule details for the app. The sub application gets generated when i run aggregation for this AD app but it doesn’t show any accounts under the sub applications.

When i tried the classic mode setup - existing AD app(master), logiplex (main app) configured the same split rule on the main app and ran aggregation for main app it generate the sub applications and it also show the accounts under the sub apps.

The only thing i can think of is that our AD app has only these feature strings “MANAGER_LOOKUP, SEARCH, UNSTRUCTURED_TARGETS, AUTHENTICATE” as the provisioning is handled by another webservices app that we have and it uses provisioning config using which all the provisioning requests sent to AD are routed to this webservices app.

Could the missing feature strings be causing issues in Adapter mode? or is there something else I’m missing?

Any help would really be appreciated.