Overview
The article describes the impact of AD/LDAP Connector integration with the CloudCache Server and the scenarios when upgrading the connector.
Applicability
Administrators using old AD/LDAP Connector versions (6.2_re48b01f9 and earlier).
User Mapping and Upgrade Considerations
The current AD/LDAP Connector (6.2_re48b01f9 & earlier) allows automatic user mapping with the CloudCache Server. However, this functionality is inoperative with the new DCP AD/LDAP Connector.
Note: The Cloud Cache server will reach its EOS on June 30, 2024. For more information, see EOS for CloudCache Server.
Upgrade Scenarios
Scenario 1: User mapped automatically to CloudCache Server with old AD/LDAP Connector
If you are using CloudCache Server mapping to automatically map users using old AD/LDAP connector and upgrades to the new AD/LDAP connector, then:
You can view the existing CloudCache mapping till its deletion.
You cannot add new CloudCache mappings.
You can map new users to existing CloudCache mappings till June 30, 2024.
Sync & Manage will continue to work as is.
Scenario 2: User mapped with CloudCache server manually using AD/LDAP old Connector and upgrades to new AD/LDAP connector
If you are usingCloudCache Server to map users manually using the old AD/LDAP connector and upgrades to the new AD/LDAP connector, then:
You can continue the user association manually.
You can add a CloudCache server manually & continue the functionality.
You cannot create a new CloudCache mapping.
Scenario 3: User mapped to CloudCache Server using the old AD/LDAP connector and do not upgrade the connector.
If you have CloudCache Server mapped with the user using AD/LDAP connector either manually or automatically and do not upgrade to a new connector, then:
You can continue using CloudCache mapping til June 30, 2024.
You can add new cache mapping based on available accounts till June 30, 2024.