Author Topic: ARSLSYNC Issues  (Read 116 times)

JeanineJ

  • Jr. Member
  • **
  • Posts: 19
ARSLSYNC Issues
« on: April 23, 2024, 09:10:38 AM »
I'm attempting to run ARSLSYNC on my RHEL7 CMOD 10.5 development box. It's been giving me fits. No matter what I do the only way I'm getting any output is with these settings in ars.cfg
ARS_LDAP_SERVER_TYPE=AD
#ARS_LDAP_USER_FILTER=(&(objectClass=user)(memberOf=CN=CMOD_XXX_Business_dev,"OU=XXXX Groups,DC=xxx,DC=xxxx,DC=xxxxx,DC=com"))
ARS_LDAP_GROUP_USER_FILTER_USE_DN=FALSE
ARS_LDAP_USER_FILTER=(objectClass=user)
ARS_LDAP_GROUP_FILTER=(objectClass=group)
ARS_LDAP_GROUP_MAPPED_ATTRIBUTE=CN
ARS_LDAP_IGN_GROUPS=Security,CMOD_Admin,CMOD_Operations
The above gives me EVERYBODY in AD except CMOD_XXX_Business_dev. I can't get the filters to work to bring in the only group with 4 users into my Dev environment. According to my identity people the group exists in AD and has 4 users defined.
If I attempt to use the USER_FILTER code ARSLSYNC doesn't find the users or group running with the just -t -v options.
Has anyone been successful using ARSLSYNC to provision users in CMOD that are part of Group?
I am in consultation with IBM Lab Services as part of a work effort to authenticate a small group of users accessing documents via the Thick Client via AD and SSL, which is working fine. Lab Services is also looking at the issue as I've sent them the trace and output.
I'm running CMOD MP 10.5.0.5 on a RHEL7 server with DB2 11
I know next to nothing about AD or LDAP.


rjrussel

  • Full Member
  • ***
  • Posts: 141
Re: ARSLSYNC Issues
« Reply #1 on: April 23, 2024, 11:12:40 AM »
You are missing the ARS_LDAP_BASE_DN parameter. Can you share that?

JeanineJ

  • Jr. Member
  • **
  • Posts: 19
Re: ARSLSYNC Issues
« Reply #2 on: April 23, 2024, 11:41:31 AM »
The BASE DN is different because we're using LDAP to authenticate the small set of users accessing documents with the Thick Client:
ARS_LDAP_BASE_DN="OU=XXXXX People,DC=XXX,DC=XXXX,DC=XXXXX,DC=com"

rjrussel

  • Full Member
  • ***
  • Posts: 141
Re: ARSLSYNC Issues
« Reply #3 on: April 23, 2024, 11:46:14 AM »
That isn't correct. Base DN needs to be DC=XXX,DC=XXXX,DC=XXXXX,DC=com

Your IBM Consultant will reach out to you.

JeanineJ

  • Jr. Member
  • **
  • Posts: 19
Re: ARSLSYNC Issues
« Reply #4 on: April 24, 2024, 07:27:12 AM »
He did and I now have an even larger list of users and groups than I had yesterday after I pulled all the filtering off the LDAP_USER_FILTER.
Enclosing the (memberOf...) statement in "" didn't help.