Moving the RSA Mobile Directory Server
Originally Published: 2005-07-26
Article Number
Applies To
Microsoft Windows 2000 Server SP4
Issue
Cause
Resolution
To change to location of the main Directory Server server that you want RSA Mobile to talk to, look at \RSASecurity\rsaappserver\properties\csf-ds-schema.xml which will look something like the following:
<def:DataStoreDef name="eTrust" driver="com.rsa.csf.techservice.datastore.driver.etrust.eTrustAdaptor">
<def:LocationDef rootContext="dc=csau,dc=ap,dc=rsa,dc=net" name="eTrust">
<protocol>ldap</protocol>
<url>ldap://192.168.51.204:19589/</url>
<secureurl>ldap://192.168.51.204:19636/</secureurl>
<location />
<principal>cn=Directory Manager,dc=csau,dc=ap,dc=rsa,dc=net</principal>
<serviceprovider>etrust</serviceprovider>
</def:LocationDef>
<def:PartDef mapFor="user" name="inetorgperson">
<def:AttributeDef name="firstName" jl:type="String" physicalName="givenName" />
<def:AttributeDef name="lastName" jl:type="String" mandatory="true" physicalName="sn" />
<def:AttributeDef name="fullName" jl:type="String" mandatory="true" physicalName="cn" />
<def:AttributeDef name="userId" jl:type="String" mandatory="true" unique="true" naturalKey="true" physicalName="uid" partofIdx="true" />
<def:AttributeDef name="emailAddress" jl:type="String" physicalName="mail" />
</def:PartDef>
</def:DataStoreDef>
<def:LocationDef rootContext="dc=csau,dc=ap,dc=rsa,dc=net" name="eTrust">
<protocol>ldap</protocol>
<url>ldap://192.168.51.204:19589/</url>
<secureurl>ldap://192.168.51.204:19636/</secureurl>
<location />
<principal>cn=Directory Manager,dc=csau,dc=ap,dc=rsa,dc=net</principal>
<serviceprovider>etrust</serviceprovider>
</def:LocationDef>
<def:PartDef mapFor="user" name="inetorgperson">
<def:AttributeDef name="firstName" jl:type="String" physicalName="givenName" />
<def:AttributeDef name="lastName" jl:type="String" mandatory="true" physicalName="sn" />
<def:AttributeDef name="fullName" jl:type="String" mandatory="true" physicalName="cn" />
<def:AttributeDef name="userId" jl:type="String" mandatory="true" unique="true" naturalKey="true" physicalName="uid" partofIdx="true" />
<def:AttributeDef name="emailAddress" jl:type="String" physicalName="mail" />
</def:PartDef>
</def:DataStoreDef>
Provided you have already used backup and restore routines to duplicate the data from the old Directory Server to the new one, and assuming it is configured with the same connection details, change the <url></url> and the <secureurl></secureurl> details to reflect the new location.
Of course, if you have a machine name in your file, then simply changing the DNS server to point the name at the new address is also valid.
Of course, if you have a machine name in your file, then simply changing the DNS server to point the name at the new address is also valid.
Is is also advisable to modify the original configuredatastore.cmd command with the changes. Although this command is used only for initial setup, it is useful for a rational system in that it reflects the current state of the system.
Related Articles
Moving the RSA Authentication Manager 8.x virtual appliance from one ESX host to another Number of Views How to enable the SSO Configuration menu in the RSA Mobile Lock Console Number of Views LDAP authenticator based on Active Directory Identity Collector fails with the error 'Connection could not be established … Number of Views Moving Users in an LDAP Directory Number of Views Directory Server Attributes Synchronized for Authentication Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records Unable to login to RSA Authentication Manager Security Console as super admin RSA Authentication Manager 8.9 Release Notes (January 2026) How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Connection fails to Cloud Authentication Service when connecting through a proxy server from RSA Authentication Manager to…
Don't see what you're looking for?
