Changing the Domain Name in Prolaborate Cloud Environment
If your organization is moving to a new domain (e.g., from @old-domain.com to @new-domain.global) and you're using Prolaborate Cloud, follow these steps for a seamless transition.
What Does a Domain Name Change Affect?
- Prolaborate login URLs
- User login recognition (preventing duplicate user accounts)
- Single Sign-On (SSO) settings
- Integration configurations (e.g., Confluence, SharePoint)
- EA model access
- Pro Cloud Server (PCS) and Floating License connections
What You Need to Do
1. Send an email to cloudsupport@prolaborate.com at least 3 business days before the domain change.
2. Include the exact new domain name format (e.g., shin.ogata@something-different.global).
3. Mention the planned domain change date.
4. Confirm SSO usage and provide contact details of the internal SSO team (if applicable).
What Prolaborate Support Will Do
In Prolaborate:
- Update the Prolaborate URL with the new domain.
- Update all user email domains in the Prolaborate database via script.
- Reconfigure SSO settings (if SAML SSO is used).
- Assist in reconfiguring integrations (e.g., Confluence, SharePoint).
In Infrastructure:
- Guide you in updating embedded Prolaborate links on external platforms (e.g., Confluence iFrames).
In PCS and Floating License Server (FLS):
- Update Pro Cloud Server connection settings.
- Update floating license server details.
- Change repository/model alias names if requested by the customer.
In Enterprise Architect (EA):
- Update user emails in the EA database via script after the domain change.
- Ensure existing access rights are retained.
What You Can Expect
- Seamless login experience without duplicate accounts.
- SSO continuity with coordination from the support team.
- Full assistance throughout the process.
- Smooth and secure domain transition.
Prolaborate SSO Configuration – SSL Certificate Handling
For cloud customers setting up SAML SSO, the Prolaborate support team is responsible for managing SSL certificates. In a reported case, the SSL certificate upload was unintentionally missed, causing delays in SSO setup.
Resolution:
- The support team uploaded the SSL certificate and updated the password.
- Once uploaded, the customer completed the SSO configuration successfully.
- If a certificate is already uploaded, it will appear in the 'Existing Certificate' section. Uploading a new file will replace the existing certificate.
Email Draft for SSL Certificate Handling
Hi <Customer>,
Thank you for reaching out.
For Prolaborate Cloud customers, SSL certificate uploads are managed by our support team. We have uploaded the required certificate and updated the password.
If the SSL certificate is already visible in the 'Existing Certificate' section, you may skip the upload and proceed with the SSO configuration. Uploading a new file will replace the existing certificate.
Please let us know if you need further assistance.
Reference Tickets
- Domain Change Process: https://desk.zoho.com/agent/sixthforcesolutions/sparx-platform-support/tickets/details/759413000010848428
- SSL Certificate Handling: https://desk.zoho.com/agent/sixthforcesolutions/sparx-platform-support/tickets/details/759413000063149001