Blog Title
IGA 15 Post migration fix for Provisioning Server and Connector Server
Product
Broadcom Symantec Identity and Access Management 15
Issue details
Post IGA 15 migration, 14.5 Provisioning Server and Connector Server are used instead of 15 Provisioning server and connector server
Possible Cause(s)
Provisioning Directory needs to be fixed.
Solution/Fix
Update the eTDSADbHost and eTDSAHost to the new provisioning server
Steps to update the provisioning server host name
- Stop Provisioning Server
- Connect to Provisioning Directory etadb via LDAP Browser/Explorer tool like Jxplorer
- Go this DN for changing provisioning server name eTDSAName=im,eTDSAContainerName=DSAs,eTNamespaceName=CommonObjects,dc=etadb
Default value for eTDSADbHost and eTDSAHost is ca-prov-srv
Change the value to IGA 15 provisioning server host name
version: 1
dn: eTDSAName=im,eTDSAContainerName=DSAs,eTNamespaceName=CommonObjects,dc=etadb
objectClass: eTDSA
eTDSAName: im
eTCreateUserid: XXXXX
eTCreateUserName: XXXXX
eTDSADbHost: <IGA 15 Provisioning Server host Name>
eTDSADbPort: 20391
eTDSADbSuffix: dc=im
eTDSADbTlsPort: 20391
eTDSAHost: <IGA 15 Provisioning Server host Name>
eTDSAPort: 20389
eTDSASuffix: dc=im
eTDSATlsPort: 20390
- Save the changes
- For cosmetic purposes,, Update the DN eTDSAName=im,eTDSAContainerName=DSAs,eTNamespaceName=CommonObjects,dc=im,dc=etadb
version: 1
dn: eTDSAName=im,eTDSAContainerName=DSAs,eTNamespaceName=CommonObjects,dc=im
,dc=etadb
objectClass: eTDSA
eTDSAName: im
eTCreateUserid: XXXXX
eTCreateUserName: XXX
eTDSADbHost: <IGA 15 Provisioning Server host Name>
eTDSADbPort: 20391
eTDSADbSuffix: dc=im
eTDSADbTlsPort: 20391
eTDSAHost: <IGA 15 Provisioning Server host Name>
eTDSAPort: 20389
eTDSASuffix: dc=im
eTDSATlsPort: 20390
- Start Provisioning Server
Workaround
None
Reference
None
Author
Rajya Tupuri