Renaming Your Okta Subdomain Skip to main content
https://support.okta.com/help/oktaarticledetailpage?childcateg=&id=ka0f0000000u4q4kak&source=documentation&refurl=http%3a%2f%2fsupport.okta.com%2fhelp%2fdocumentation%2fknowledge_article%2frenaming-your-okta-subdomain
How satisfied are you with the Okta Help Center?
Thank you for your feedback!
How satisfied are you with the Okta Help Center?
1
2
3
4
5
Very Dissatisfied
Very satisfied
Enter content less than 200 characters.
Renaming Your Okta Subdomain
Published: Jun 30, 2015   -   Updated: Jun 22, 2018

Due to re-branding, merger and acquisition activity or other organizational initiatives, customers may need to rename their existing Okta subdomain (i.e., mycompany.okta.com to company.okta.com). The following steps should serve as a overview of items to change when renaming your organization's Okta subdomain.

Please contact Okta Support to check availability of the new subdomain and coordinate timing to rename your organization's subdomain. Once your Okta subdomain has been renamed, the following tasks MUST be completed to ensure proper functionality. Proper planning of your Okta subdomain renaming effort should help to minimize service disruptions.

 
  • AD Agents: If your organization has integrated Okta with Active Directory, each AD agent for each domain must be uninstalled/reinstalled using the new Okta subdomain.  

Refer to the Installing and Configuring the Active Directory Agent guide for detailed instructions for uninstalling/reinstalling your AD agent(s).

  • LDAP Agents: If your organization has integrated Okta with an LDAP Directory, each LDAP agent must be uninstalled/reinstalled using the new Okta subdomain.

Refer to the LDAP Agent Deployment Guide for details instructions on installing your LDAP agent.

  • Desktop SSO: If your organization has configured Okta for Desktop Single Sign-On, each IWA server must be uninstalled/reinstalled using the new Okta subdomain.

Refer to the Configuring Desktop SSO guide for detailed instructions on installing your IWA server.

  • Radius Agent: If your organization has configured Okta with RADIUS, each Okta RADIUS agent must be uninstalled/reinstalled using the new Okta subdomain.

Refer to the Installing the Okta RADIUS Agent guide for detailed instructions on uninstalling/reinstalling your Okta RADIUS agent.

  • RSA SecurID Agent: If your organization has configured Okta with RSA SecurID, each RSA SecurID agent must be uninstalled/reinstalled using the new Okta subdomain.

Refer to the Installing and Configuring the Okta Radius Agent guide for detailed instructions on uninstalling/reinstalling your Okta RSA SecurID agent.

  • API: If your organization is using any Okta API tokens for making REST API calls, the tokens need not be regenerated, but special care must be taken to update any custom code to ensure the API end-points reference the new Okta subdomain.

  • SSO Applications: If your organization has configured any SAML or WS-Fed integrated applications,  review the SAML or WS-Fed Sign-On setup instructions fore each application. You will need to update each SAML or WS-Fed Service Provider integration with the corrected Okta subdomain to ensure there are no disruptions in SSO logins.

  • Okta Verify: If your organization uses Okta Verify as an MFA option, all Okta Verify with Push Authentication enrollments must be reset.

Refer to Using Okta Verify for instructions to reset your end-users' MFA.