TCPWave customers can also choose to have all the three providers listed above to provide cloud DNS hosting for every DNS zone managed by TCPWave IPAM. DNS Zones created in the TCPWave IPAM support Zone Mirroring with Amazon’s Route 53 DNS, Rackspace DNS and Google DNS. DNS records added to the TCPWave IPAM are automatically synchronized with the cloud providers listed above using TCPWave’s powerful RestAPI methods. The management communication uses encrypted SSL thereby preventing man in the middle attacks. Contact us to schedule a demo.
The NADM and PADM users can perform Add/Modify/Delete Operations on the Web Interface. However, these operations are termed as workflows and are staged for approvals by SADM or FADM users. Every workflow action that is staged will be entitled with a unique workflow identification number. Any change ticket number that has been entered at the beginning of the session will also be automatically pulled into the data by tracking the HTTP Header.
SADM and FADM users can login to the workflow management web interface and review the data. Only these users will have the privilege to Approve/Deny a workflow. A workflow that has been approved or denied cannot be revoked since the workflow manager asynchronously delegates the action to the appropriate service handler for execution upon approval. However, the underlying entity can be revoked using the Undo Functionality.
TCPWave Facilitates the Process for Quick Integration The initial configuration of TCPWave and Microsoft integration is simplified by an easy-to-follow wizard that helps quickly guide the administrative team through the process of establishing communication between the two systems. When integration is established, TCPWave provides additional logging and tests to monitor the synchronization processes and provide an audit of AD site activities. An organization has the option to configure integration in read-only mode or read/write mode in order to actively manage and optimize AD sites. TCPWave uses role-based access controls based on Microsoft AD groups to determine which administrative teams are authorized to make changes within the TCPWave tool set. When TCPWave first communicates with Microsoft AD Sites and Services, it imports the current AD site configuration. From then on, any changes that are configured from within Microsoft Management Console will be continuously synchronized within TCPWave as incremental updates. Likewise, any networks created within TCPWave and assigned to an AD site will be synchronized within Microsoft AD Sites and Services.