Difference between revisions of "Customising your domain"
Jump to navigation
Jump to search
(Created page with "==Customising your domain== By default, Studentnet will set your Login Page and your Cloudwork.ID Service Page domains: <br>File:demo_login_page.PNG|300px|centre|frame|Examp...") |
|||
| (11 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | ==Customising your domain== | + | ==Customising your domain for Login Page and Cloudwork.ID Page== |
| − | + | Studentnet will create your Login Page domain and your Cloudwork.ID Page domain ''(more info on what is Cloudwork.ID is located [https://wiki.studentnet.net/index.php/Cloudwork.ID here])''. <br>[[File:demo_login_page.PNG|300px|centre|frame|Example of Login Page Domain]]<br>[[File:demo_CloudworkID_page.PNG|300px|centre|frame|Example of Cloudwork.ID Page Domain]] | |
| − | If your school wishes to use a customised domain for the Login Page and the Cloudwork.ID | + | If your school wishes to use a customised domain for the Login Page domain and the Cloudwork.ID Page domain the following steps will need to be completed. |
==Adding DNS Entries to your domain== | ==Adding DNS Entries to your domain== | ||
| − | #Contact the person in charge of adding DNS Entries to your domain. | + | #Contact the person in charge of adding DNS Entries to your school's domain. |
#Request the addition of the following CNAME records: | #Request the addition of the following CNAME records: | ||
| − | #: '''<Login Domain>''' ''(This will be the Login Page domain you want users to login in with)'' CNAME proxy.cloudworkengine.net. | + | #: '''<Login Page Domain>''' ''(This will be the Login Page domain you want users to login in with)'' CNAME proxy.cloudworkengine.net. |
| − | #: '''< | + | #: '''<Cloudwork.ID Page domain>''' ''(This will be the Cloudwork.ID Page domain for the users accessing the Cloudwork.ID Page)'' CNAME proxy.cloudworkengine.net. |
| − | |||
===Email Template asking for CNAME creations=== | ===Email Template asking for CNAME creations=== | ||
<blockquote> | <blockquote> | ||
| − | Hi '''<Whom this may concern>''' | + | Hi '''<Whom this may concern>''' <br> |
| − | + | For my school's domain '''<school's domain name>''', could you please add the following CNAME records:<br> | |
| − | For my domain '''<domain name>''', could you please add the following CNAME records:<br> | + | '''<Login Page Domain>''' pointing to proxy.cloudworkengine.net.<br> |
| − | '''<Login Domain>''' pointing to proxy.cloudworkengine.net.<br> | + | '''<Cloudwork.ID Page domain>''' pointing to proxy.cloudworkengine.net. |
| − | '''< | ||
</blockquote> | </blockquote> | ||
| − | |||
==Sending support ticket== | ==Sending support ticket== | ||
| − | #Once your domain has been updated with the CNAME records, create a new ticket with studentnet ('''[https://support.studentnet.net/support/tickets/new Create support ticket here]''') | + | #Once your school's domain has been updated with the CNAME records, create a new ticket with studentnet ('''[https://support.studentnet.net/support/tickets/new Create support ticket here]''') |
| − | #Ask studentnet to customise | + | #Ask studentnet to customise the domain for the Login Page and Cloudwork.ID Page |
===Ticket Template=== | ===Ticket Template=== | ||
<blockquote> | <blockquote> | ||
| − | Hi Support, | + | Hi Support,<br> |
| + | '''<School>''' is wanting to have customised domains for our Login page and Cloudwork.ID Page <br> | ||
| + | The domain for Login Page: '''<Login Page Domain>'''<br> | ||
| + | The domain for Cloudwork.ID Page: '''<Cloudwork.ID Page domain>''' | ||
| + | </blockquote> | ||
| − | ''' | + | ==Migration of existing Single Sign On Services== |
| − | + | '''Disclaimer''': If you have existing Single Sign On Services configured, each existing Single Sign On Service will need to be reconfigured. | |
| − | The | + | '''The steps for reconfiguration will depend on each Single Sign On Service'''<br> |
| − | + | The reason for needing to reconfigure all existing services is because changing domains for Login Page and Cloudwork.ID Page will change the metadata information that is used for Single Sign On.<br> | |
| + | Since the metadata information has been changed, all existing Single Sign On Services will require the updated metadata information. | ||
| + | |||
| + | [[Category: Cloudwork Setup]] | ||
Latest revision as of 07:05, 22 September 2021
Contents
Customising your domain for Login Page and Cloudwork.ID Page
Studentnet will create your Login Page domain and your Cloudwork.ID Page domain (more info on what is Cloudwork.ID is located here).
Example of Login Page Domain
Example of Cloudwork.ID Page Domain
If your school wishes to use a customised domain for the Login Page domain and the Cloudwork.ID Page domain the following steps will need to be completed.
Adding DNS Entries to your domain
- Contact the person in charge of adding DNS Entries to your school's domain.
- Request the addition of the following CNAME records:
- <Login Page Domain> (This will be the Login Page domain you want users to login in with) CNAME proxy.cloudworkengine.net.
- <Cloudwork.ID Page domain> (This will be the Cloudwork.ID Page domain for the users accessing the Cloudwork.ID Page) CNAME proxy.cloudworkengine.net.
Email Template asking for CNAME creations
Hi <Whom this may concern>
For my school's domain <school's domain name>, could you please add the following CNAME records:
<Login Page Domain> pointing to proxy.cloudworkengine.net.
<Cloudwork.ID Page domain> pointing to proxy.cloudworkengine.net.
Sending support ticket
- Once your school's domain has been updated with the CNAME records, create a new ticket with studentnet (Create support ticket here)
- Ask studentnet to customise the domain for the Login Page and Cloudwork.ID Page
Ticket Template
Hi Support,
<School> is wanting to have customised domains for our Login page and Cloudwork.ID Page
The domain for Login Page: <Login Page Domain>
The domain for Cloudwork.ID Page: <Cloudwork.ID Page domain>
Migration of existing Single Sign On Services
Disclaimer: If you have existing Single Sign On Services configured, each existing Single Sign On Service will need to be reconfigured.
The steps for reconfiguration will depend on each Single Sign On Service
The reason for needing to reconfigure all existing services is because changing domains for Login Page and Cloudwork.ID Page will change the metadata information that is used for Single Sign On.
Since the metadata information has been changed, all existing Single Sign On Services will require the updated metadata information.
