Setting up a new sub-provider - Revision history

Regify: /* SSL Certificate */

2024-12-13T08:14:52Z

SSL Certificate

Regify: /* SSL Certificate */

2024-12-13T08:09:53Z

SSL Certificate

Regify: /* ToDo's */

2020-05-14T15:25:02Z

ToDo's

Regify: /* Network */

2020-05-14T15:22:14Z

Network

Regify: /* Setting up in web administration */

2020-05-14T15:20:19Z

Setting up in web administration

Regify: /* Setting up in web administration */

2019-09-27T09:45:49Z

Setting up in web administration

Regify: /* Certificate */

2019-09-27T09:44:52Z

Certificate

Regify at 10:15, 19 August 2019

2019-08-19T10:15:23Z

Regify at 08:40, 14 May 2018

2018-05-14T08:40:23Z

Regify: /* Certificate */

2018-02-19T13:02:15Z

Certificate

@@ Line 22: / Line 22: @@
 # If received, collect the certificate and all intermediate certificates in a text editor.
 # Import certificate using "Import Cert & Optionally Key" from appliance menu and paste text editor content.
-# Check correct certificate chain here at [https://www.geocerts.com/ssl-checker geocerts] (maybe only possible after you finished setup).
+# Check correct certificate chain here at [https://www.sslshopper.com/ssl-checker.html sslshopper] (maybe only possible after you finished setup).
 == Setting up the subprovider ==

@@ Line 22: / Line 22: @@
 # If received, collect the certificate and all intermediate certificates in a text editor.
 # Import certificate using "Import Cert & Optionally Key" from appliance menu and paste text editor content.
-# Check correct certificate chain here at [http://www.digicert.com/help/ digicert] (maybe only possible after you finished setup).
+# Check correct certificate chain here at [https://www.geocerts.com/ssl-checker geocerts] (maybe only possible after you finished setup).
 == Setting up the subprovider ==

@@ Line 56: / Line 56: @@
 === ToDo's ===
-When the new admin logs into the web administration function, he / she will see some ToDo's. Please follow these to make sure that everything is set up correctly. Do not click on "Done" if all tasks are not really done.
+When the new admin logs into the web administration function, he / she will see some ToDo's. '''Please follow these ToDos''' to make sure that everything is set up correctly. Do not click on "Done" if all tasks are not really done.
 == Delete a subprovider ==

@@ Line 4: / Line 4: @@
 === Network ===
-# You need a new public IPv4 IP address for a subprovider.
+# You need a new public IPv4 IP address for a new subprovider.
 # If the regify provider is directly connected to the internet
 #* Enter the public IP to the regify provider appliance

@@ Line 36: / Line 36: @@
 # If the provider system is running a cross-master replication, ensure that you also configure the other system in the same manner.
-=== Setting up in web administration ===
+=== Continue set up in web administration ===
 After setting up the system in the appliance menu (on all systems), you can continue with the setup by using the web administration

@@ Line 39: / Line 39: @@
 After setting up the system in the appliance menu (on all systems), you can continue with the setup by using the web administration
-# Login to the web administration of the main provider as a master admin and select "Manage subproviders". The new subprovider should appear in the list of subproviders.
+# Login to the web administration of the main(!) provider as a master admin and select "Manage subproviders". The new subprovider should appear in the list of subproviders.
 # Selecting the new subprovider in the list of subproviders allows you to edit the settings in the lower area "Edit provider settings".
 # Complete the settings of the new subprovider and finish it by clicking "Save changes".

@@ Line 13: / Line 13: @@
 # If your provider appliance runs with its own MTA settings (one setting for all (sub)provider instances), you will also need a reverse DNS entry for email to make it work. Also, SPF records may be needed.
-=== Certificate ===
+=== SSL Certificate ===
-How to buy a SSL certificate for the subprovider domain:
+If you already have a SSL certificate for the subprovider domain, you can import the certificate after the subprovider was created. This works with individual and wildcard certificates.
 # Whilst setting up the new subprovider in your appliance menu, a new certificate is generated.
 # You can display the signing request by choosing "Show Cert Request" in the appliance menu. Fill in the fields.
 # Copy and use the signing request to order your certificate.
 # If received, collect the certificate and all intermediate certificates in a text editor.
-# Import certificate using "Import Cert & Optionally Key" from appliance menu and past text editor content.
+# Import certificate using "Import Cert & Optionally Key" from appliance menu and paste text editor content.
 # Check correct certificate chain here at [http://www.digicert.com/help/ digicert] (maybe only possible after you finished setup).

@@ Line 1: / Line 1: @@
 == Prerequisites and information ==
-'''IMPORTANT:''' Before setting up a new sub-provider, please read the generic article about sub-providers: [[Subprovider]]
+'''IMPORTANT:''' Before setting up a new subprovider, please read the generic article about subproviders: [[Subprovider]]
 === Network ===
-# You need a new public IPv4 IP address for a sub-provider.
+# You need a new public IPv4 IP address for a subprovider.
 # If the regify provider is directly connected to the internet
 #* Enter the public IP to the regify provider appliance
 # If the regify provider is behind a firewall / NAT router / Loadbalancer
 #* The public IP must be configured to route to your regify provider software appliance or load-balancer (depending on your configuration).
-#* Internal routing IP address must get added in provider appliance menu.
+#* Internal routing IP address must be added into the provider appliance menu.
-# A new DNS A-record must be made to route your new domain (like sub-provider.company.com) to the new public IP address.
+# A new DNS A-record must be made to route your new domain (like subprovider.company.com) to the new public IP address.
-# If your provider appliance runs with own MTA settings (one setting for all (sub)provider instances), you also need a reverse DNS entry for email to make it work. Also, SPF records may be needed.
+# If your provider appliance runs with its own MTA settings (one setting for all (sub)provider instances), you will also need a reverse DNS entry for email to make it work. Also, SPF records may be needed.
 === Certificate ===
-How to buy a SSL certificate for the needed sub-provider domain:
+How to buy a SSL certificate for the subprovider domain:
-# While setting up the new sub-provider in your appliance menu, a new certificate is generated.
+# Whilst setting up the new subprovider in your appliance menu, a new certificate is generated.
-# You can display the signing request by choosing "Show Cert Request" in appliance menu. Fill in the fields.
+# You can display the signing request by choosing "Show Cert Request" in the appliance menu. Fill in the fields.
 # Copy and use the signing request to order your certificate.
 # If received, collect the certificate and all intermediate certificates in a text editor.
@@ Line 22: / Line 22: @@
 # Check correct certificate chain here at [http://www.digicert.com/help/ digicert] (maybe only possible after you finished setup).
-== Setting up the sub-provider ==
+== Setting up the subprovider ==
 Please ensure that all prerequisites are fulfilled. Now follow these steps:
 === Setting up in appliance menu ===
 # Enter appliance menu and chose "Network..." -> "Add IP" to add the public IP address (if not yet done).
-# Enter "Provider..." -> "Add sub-provider" option.
+# Enter "Provider..." -> "Add subprovider" option.
-# Choose the added IP address (internal address if behind firewall, router or load-balancer).
+# Choose the IP address added (internal address if behind firewall, router or load-balancer).
-# Enter the server name of the new sub-provider and answer all questions asked by the system.
+# Enter the server name of the new subprovider and answer all questions asked by the system.
-# Select "Edit Subprovider..." in the appliance menu and chose the added sub-provider from the menu
+# Select "Edit Subprovider..." in the appliance menu and chose the added subprovider from the menu.
-# Import the SSL certificate using "Import Cert & Optionally key" from the appliance menu (not needed if the load balancer holds the certificates)
+# Import the SSL certificate using "Import Cert & Optionally key" from the appliance menu (not needed if the load balancer holds the certificates).
-# If the provider system is running a cross-master replication, ensure that you also configure the other system in the same manner
+# If the provider system is running a cross-master replication, ensure that you also configure the other system in the same manner.
 === Setting up in web administration ===
 After setting up the system in the appliance menu (on all systems), you can continue with the setup by using the web administration
-# Login to the web administration of the main provider as a master admin and select "Manage sub-providers". The new sub-provider should appear in the list of sub-providers
+# Login to the web administration of the main provider as a master admin and select "Manage subproviders". The new subprovider should appear in the list of subproviders.
-# Selecting the new sub-provider in the list of sub-providers allows you to edit the settings in the lower area "Edit provider settings"
+# Selecting the new subprovider in the list of subproviders allows you to edit the settings in the lower area "Edit provider settings".
-# Complete the settings of the new sub-provider and finish it by clicking "Save changes"
+# Complete the settings of the new subprovider and finish it by clicking "Save changes".
 === Admin-Account and Customization ===
-Upon successful sub-provider creation, you need some administrator user for this sub-provider to edit customization:
+Once the subprovider has been successfully created, you need an administrator user for this subprovider to edit and do customization:
-# Let the new admin sign up for a regify account on the new sub-provider.
+# New admin signs up for a regify account on the new subprovider.
 # Activate from the email and note your password.
-# Login to main(!) provider administration -> "Manage sub-providers" (with existing main(!) provider admin account).
+# Login to main(!) provider administration -> "Manage subproviders" (with existing main(!) provider admin account).
-# Go "Manage sub-providers".
+# Go to "Manage subproviders".
-# Select the sub-provider in the list to add the admin user to.
+# Select the subprovider in the list to add the admin user to.
 # Click on "Manage portal administration roles" in the "Common" tab below.
-# Enter the new user as "Sub-Provider Admin" (you can user the "..." button to search the user ID).
+# Enter the new user as "Subprovider Admin" (you can user the "..." button to search the user ID).
-# Log-out from administration.
+# Log-out from administration screen.
-# The new admin now can log-in to https://sub-provider-domain/ADMINISTRATION
+# The new admin now can log-in to https://subprovider-domain/ADMINISTRATION
 === ToDo's ===
-Upon the new admin log-in to his web-administration, he will see some ToDo's for sure. Please follow these to make sure that everything is set up correctly. Do not only click on "Done" if it is not really done.
+When the new admin logs into the web administration function, he / she will see some ToDo's. Please follow these to make sure that everything is set up correctly. Do not click on "Done" if all tasks are not really done.
-== Delete a sub-provider ==
+== Delete a subprovider ==
-In order to get deleted, a sub-provider must be empty. So saying, not a single user is assigned to this sub-provider anymore. Normally, all users are getting exported/imported to some other system or moved to another sub-provider.
+In order to  delete a subprovider, it must be emptied of all data. Thus, not a single user will be assigned to this subprovider anymore. The first step is usually to export/import all users to some other system or moved to another subprovider.
-Finally, only admin accounts are left. Please follow these steps to get rid of the sub-providers admin users:
+Finally, this leaves only admin accounts. Please follow these steps to get rid of the subprovider's admin users:
-# You first have to enter the main provider administration with "master" admin role and remove any admin roles for the affected sub-provider except the one for the last and final administrator of the sub-provider.
+# You first have to enter the main provider administration portal in the "master" admin role and remove any admin roles for the affected subprovider except the one for the last and final administrator of the subprovider.
-# Now, log-in with this last admin user to the sub-provider administration.
+# Now, log-in with this last admin user name to the subprovider administration screen.
-# Enter "Manage user" and do a simple search. Only the single admin should come up (you). You can not delete this account, because it is still an admin!
+# Enter "Manage user" and do a simple search. Only the single admin should come up now (you). You cannot delete this account, because it is still an admin!
 # Select "Action" - "Change the user data"
-# On the bottom of the dialog, please switch the "Sub-Provider" to the main provider domain and click on "Save changes".
+# On the bottom of the dialogue box, please switch the "Subprovider" to the main provider domain and click on "Save changes".
 # Now, please close the window, go back to main page and log out.
-# Now, you have to enter the main provider administration with "master" admin role and finally remove the admin role for the affected sub-provider. The "Master" role of the main provider admin may stay here and may not get deleted.
+# Now, you have to enter the main provider administration portal in the "master" admin role and finally remove the admin role for the affected subprovider. The "Master" role of the main provider admin stays here and does not get deleted.
-Finally, the sub-provider can get deleted by the SSH appliance menu.
+Finally, the subprovider can be deleted by the SSH appliance menu.

← Older revision		Revision as of 08:40, 14 May 2018
Line 55:		Line 55:
	=== ToDo's ===		=== ToDo's ===
	Upon the new admin log-in to his web-administration, he will see some ToDo's for sure. Please follow these to make sure that everything is set up correctly. Do not only click on "Done" if it is not really done.		Upon the new admin log-in to his web-administration, he will see some ToDo's for sure. Please follow these to make sure that everything is set up correctly. Do not only click on "Done" if it is not really done.
		+
		+	== Delete a sub-provider ==
		+	In order to get deleted, a sub-provider must be empty. So saying, not a single user is assigned to this sub-provider anymore. Normally, all users are getting exported/imported to some other system or moved to another sub-provider.
		+
		+	Finally, only admin accounts are left. Please follow these steps to get rid of the sub-providers admin users:
		+
		+	# You first have to enter the main provider administration with "master" admin role and remove any admin roles for the affected sub-provider except the one for the last and final administrator of the sub-provider.
		+	# Now, log-in with this last admin user to the sub-provider administration.
		+	# Enter "Manage user" and do a simple search. Only the single admin should come up (you). You can not delete this account, because it is still an admin!
		+	# Select "Action" - "Change the user data"
		+	# On the bottom of the dialog, please switch the "Sub-Provider" to the main provider domain and click on "Save changes".
		+	# Now, please close the window, go back to main page and log out.
		+	# Now, you have to enter the main provider administration with "master" admin role and finally remove the admin role for the affected sub-provider. The "Master" role of the main provider admin may stay here and may not get deleted.
		+
		+	Finally, the sub-provider can get deleted by the SSH appliance menu.