You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/multifactor-authentication/administrator/customizing-widget.md
+40
Original file line number
Diff line number
Diff line change
@@ -9,3 +9,43 @@ You may change the logo and the friendly name that is displayed to your users. T
9
9
10
10
***Friendly Name**: the name of the app that you want displayed to users
11
11
***Logo URL**: the URL that points to the logo image you want displayed to users
12
+
13
+
## Customizing the Guardian Landing Page
14
+
15
+
### Activate the Hosted Page
16
+
17
+
Customizing the content of the Guardian widget page is possible in the [Guardian Multifactor Hosted Page](${manage_url}/#/guardian_mfa_page) by toggling _Customize Guardian Page_.
There are a few theming options for _mfa-widget_, namespaced under the `theme` property.
23
+
24
+
#### icon
25
+
The value for `icon` is the URL for an image that will be used in the _mfa-widget_ header, which defaults to the Auth0 logo. It has a recommended max height of `58px` for a better user experience.
26
+
27
+
```js
28
+
theme: {
29
+
icon:'https://example.com/assets/logo.png'
30
+
},
31
+
```
32
+
33
+
#### primaryColor
34
+
The `primaryColor` property defines the primary color of the _mfa-widget_. This option is useful when providing a custom `icon`, to ensure all colors go well together with the `icon`'s color palette. Defaults to `#ea5323`.
35
+
36
+
```js
37
+
theme: {
38
+
icon:'https://example.com/assets/logo.png',
39
+
primaryColor:'blue'
40
+
},
41
+
```
42
+
43
+
### Rendering "Invited Enrollments" vs. Standard Scenarios
44
+
There are two different possible scenarios in which the page is rendered. If a user has been directed to this page specifically for enrollment (for instance, from an email with an enrollment link) then the property **ticket** will be available. Otherwise, the property **requestToken** will be available.
45
+
46
+
### HTML + Liquid syntax
47
+
48
+
The hosted page uses [Liquid](https://github.com/Shopify/liquid/wiki/Liquid-for-Designers) syntax for templating.
49
+
The following parameters are available to assist in rendering your page: **userData.email**, **userData.friendlyUserId**, **userData.tenant**, **userData.tenantFriendlyName**, **iconUrl**.
50
+
Most of the parameters that are used in MFA-Widget need to be passed to Guardian as shown in the default template provided in the customization area.
51
+
If you need a higher level of customization you could use [auth0-guardian.js](https://github.com/auth0/auth0-guardian.js/tree/master/example).
The user will receive an enrollment email at their registered email address.
17
+
18
+
Administrators can also [customize the email template](/email/templates) for the enrollment emails.
19
+
20
+
## Restricting user-initiated enrollments
21
+
22
+
Some organizations may want to only allow users to enroll a device with Guardian via an enrollment email, and prevent users from self-enrolling upon first sign in. This is possible using the _selfServiceEnrollment_ property on a Guardian rule. When set to true, or when the property is not set, the user may self-enroll. When set to false, the user may only enroll their device via an enrollment email.
23
+
24
+
To edit the rule, go to the **Multifactor Auth** section and edit appropriately.
0 commit comments