-
Hosting Guidelines
The D2L Brightspace Cloud provides a continuous delivery model where your environment is deployed and updated without impact to performance or availability for end users. When implementing your Brightspace in the D2L Brightspace Cloud, by default, a domain managed by D2L is provided for your site access. Standard…
-
Default URL and Backup Configurations
Default URL Configurations A Brightspace is initially configured using a D2L-managed domain, typically with the format orgname.brightspace.com. Default Brightspace domain configurations are secured with an SSL certificate, typically a wildcard Brightspace.com certificate, and configured to respect the latest TLS connection…
-
Using a Custom URL to access Brightspace
You can configure a custom URL, such as d2l.example.com, to access your Brightspace. One custom URL (the primary URL) is supported for site access and navigation. The Brightspace environment is configured to use the primary URL on your behalf during implementation, or when you request a change to the primary URL. You can…
-
Securing a custom URL with an auto-renewing SSL Certificate
For clients hosted within the D2L AWS regions, the AWS Certificate manager can generate certificates for custom URLs. This allows D2L to generate, renew, and deploy SSL certificates to the D2L servers on behalf of our clients without added cost. To provide validation that D2L can manage certificates on behalf of your…
-
Using a custom mail domain
A custom mail domain, such as mail.mycourses.client.com, can be configured as the default outgoing mail domain in your Brightspace environment. As a best practice, the custom mail domain should be used in configurations for sending system emails and notification emails. Other options, such as your Helpdesk Display Name or…
-
Default Mail Configurations
Brightspace is configured using a mail subdomain of the default URL, typically with the format mail.orgname.brightspace.com. Default Brightspace mail configurations are used as the FromAddress domain for sending system emails, notification emails, and user generated emails. * System emails will appear to come from: From:…
-
Using publicly certified and accessible LDAP servers
To enable a simple and secure configuration when using the D2L Lightweight Directory Access Protocol (LDAP) Authentication method, your LDAP server should be publicly accessible and have an SSL certificate installed. Using a certificate generated by a Public Certificate Authority means you are not required to coordinate…
-
Local Approved Domain Login
Administrators can also set up a custom authentication method for allowing a list of approved usernames. When the authentication method is enabled, only users defined within the approved list can log in using the D2L Local Login. Users that cannot be authenticated using the client LDAP settings are blocked from logging in.…