cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
230
Views
0
Helpful
1
Replies
Beginner

CMS Access methods under a space

Assuming you have LDAP synced users on CMS and wish to change the JiDMapping (as part of the LDAP mapping) I understand you would need to LDAP sync for this new mapping to take effect.

 

If LDAP synced users have an AccessMethod defined under their space will these access methods be lost when another LDAP sync is performed (after changing JidMapping value ). Or will all the access methods for each user be maintained following subsequent LDAP Sync.

Thanks

Everyone's tags (2)
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Beginner

Re: CMS Access methods under a space

We have CMS 2.6.1 and I done a test

 

There were the next options:

<ldapMapping id="ca87ebb1-f53e-4946-9d9d-cf62bab814bc">
<jidMapping>$mail$</jidMapping>
<nameMapping>$cn$</nameMapping>
<cdrTagMapping></cdrTagMapping>
<coSpaceNameMapping>$sAMAccountName$ Space</coSpaceNameMapping>
<coSpaceUriMapping>$sAMAccountName$.space</coSpaceUriMapping>
<coSpaceSecondaryUriMapping></coSpaceSecondaryUriMapping>
<coSpaceCallIdMapping></coSpaceCallIdMapping>
<authenticationIdMapping>$userPrincipalName$</authenticationIdMapping>
</ldapMapping>

 

<coSpace id="73b60a63-d56e-47cd-9168-7a5c0d79354a">
<name>user Space</name>
<autoGenerated>true</autoGenerated>
<uri>user.space</uri>
<callId></callId>
<nonMemberAccess>true</nonMemberAccess>
<ownerId>218b55ea-b9b8-4d47-862c-6d833ad7597a</ownerId>
<ownerJid>user@company.ru</ownerJid>

<numAccessMethods>1</numAccessMethods>
</coSpace>

 

<accessMethods total="1">
<accessMethod id="7132a99a-b030-4ee4-9ec0-3389fe61e144">
<uri>88888888</uri>
<callId></callId>
<passcode></passcode>
</accessMethod>
</accessMethods>

 

I changed the ldapMapping's jidMapping

<ldapMapping id="ca87ebb1-f53e-4946-9d9d-cf62bab814bc">
<jidMapping>$sAMAccountName$@new.com</jidMapping>
<nameMapping>$cn$</nameMapping>
<cdrTagMapping></cdrTagMapping>
<coSpaceNameMapping>$sAMAccountName$ Space</coSpaceNameMapping>
<coSpaceUriMapping>$sAMAccountName$.space</coSpaceUriMapping>
<coSpaceSecondaryUriMapping></coSpaceSecondaryUriMapping>
<coSpaceCallIdMapping></coSpaceCallIdMapping>
<authenticationIdMapping>$userPrincipalName$</authenticationIdMapping>
</ldapMapping>

 

I performed new sync, CMS didn't recreate user's space, it modifed it

<coSpace id="73b60a63-d56e-47cd-9168-7a5c0d79354a">
<name>user Space</name>
<autoGenerated>true</autoGenerated>
<uri>user.space</uri>
<callId>639550835</callId>
<nonMemberAccess>true</nonMemberAccess>
<ownerId>218b55ea-b9b8-4d47-862c-6d833ad7597a</ownerId>
<ownerJid>user@new.com</ownerJid>
<numAccessMethods>1</numAccessMethods>
</coSpace>

 

coSpaces wasn't deleted and there is our old accessMethods in it.

 

So, all the access methods for each user will be maintained following subsequent LDAP Sync.

 

1 REPLY 1
Highlighted
Beginner

Re: CMS Access methods under a space

We have CMS 2.6.1 and I done a test

 

There were the next options:

<ldapMapping id="ca87ebb1-f53e-4946-9d9d-cf62bab814bc">
<jidMapping>$mail$</jidMapping>
<nameMapping>$cn$</nameMapping>
<cdrTagMapping></cdrTagMapping>
<coSpaceNameMapping>$sAMAccountName$ Space</coSpaceNameMapping>
<coSpaceUriMapping>$sAMAccountName$.space</coSpaceUriMapping>
<coSpaceSecondaryUriMapping></coSpaceSecondaryUriMapping>
<coSpaceCallIdMapping></coSpaceCallIdMapping>
<authenticationIdMapping>$userPrincipalName$</authenticationIdMapping>
</ldapMapping>

 

<coSpace id="73b60a63-d56e-47cd-9168-7a5c0d79354a">
<name>user Space</name>
<autoGenerated>true</autoGenerated>
<uri>user.space</uri>
<callId></callId>
<nonMemberAccess>true</nonMemberAccess>
<ownerId>218b55ea-b9b8-4d47-862c-6d833ad7597a</ownerId>
<ownerJid>user@company.ru</ownerJid>

<numAccessMethods>1</numAccessMethods>
</coSpace>

 

<accessMethods total="1">
<accessMethod id="7132a99a-b030-4ee4-9ec0-3389fe61e144">
<uri>88888888</uri>
<callId></callId>
<passcode></passcode>
</accessMethod>
</accessMethods>

 

I changed the ldapMapping's jidMapping

<ldapMapping id="ca87ebb1-f53e-4946-9d9d-cf62bab814bc">
<jidMapping>$sAMAccountName$@new.com</jidMapping>
<nameMapping>$cn$</nameMapping>
<cdrTagMapping></cdrTagMapping>
<coSpaceNameMapping>$sAMAccountName$ Space</coSpaceNameMapping>
<coSpaceUriMapping>$sAMAccountName$.space</coSpaceUriMapping>
<coSpaceSecondaryUriMapping></coSpaceSecondaryUriMapping>
<coSpaceCallIdMapping></coSpaceCallIdMapping>
<authenticationIdMapping>$userPrincipalName$</authenticationIdMapping>
</ldapMapping>

 

I performed new sync, CMS didn't recreate user's space, it modifed it

<coSpace id="73b60a63-d56e-47cd-9168-7a5c0d79354a">
<name>user Space</name>
<autoGenerated>true</autoGenerated>
<uri>user.space</uri>
<callId>639550835</callId>
<nonMemberAccess>true</nonMemberAccess>
<ownerId>218b55ea-b9b8-4d47-862c-6d833ad7597a</ownerId>
<ownerJid>user@new.com</ownerJid>
<numAccessMethods>1</numAccessMethods>
</coSpace>

 

coSpaces wasn't deleted and there is our old accessMethods in it.

 

So, all the access methods for each user will be maintained following subsequent LDAP Sync.

 

CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards