Two-factor authentication (2FA) for Umbraco members is activated by implementing an ITwoFactorProvider interface and registering the implementation. The implementation can use third-party packages to archive for example support for authentication apps like Microsoft- or Google Authentication App.
If you are using , you can enable multi-factor authentication in Umbraco ID. For more information, see the article.
Two-factor authentication for Members
Since Umbraco does not control how the UI is for member login and profile edit. The UI for 2FA is shipped as part of the Partial View snippets. These can be used as a starting point, before styling the page as you would like.
Example implementation for Authenticator Apps for Members
In the following example, we will use the .
Despite the name, this package works for both Google and Microsoft authenticator apps. It can be used to generate the QR code needed to activate the app for the website.
UmbracoAppAuthenticator.cs
using System;
using System.Threading.Tasks;
using Google.Authenticator;
using Umbraco.Cms.Core.Security;
using Umbraco.Cms.Core.Services;
namespace My.Website;
/// <summary>
/// Model with the required data to setup the authentication app.
/// </summary>
public class QrCodeSetupData
{
/// <summary>
/// The secret unique code for the user and this ITwoFactorProvider.
/// </summary>
public string Secret { get; init; }
/// <summary>
/// The SetupCode from the GoogleAuthenticator code.
/// </summary>
public SetupCode SetupCode { get; init; }
}
/// <summary>
/// App Authenticator implementation of the ITwoFactorProvider
/// </summary>
public class UmbracoAppAuthenticator : ITwoFactorProvider
{
/// <summary>
/// The unique name of the ITwoFactorProvider. This is saved in a constant for reusability.
/// </summary>
public const string Name = "UmbracoAppAuthenticator";
private readonly IMemberService _memberService;
/// <summary>
/// Initializes a new instance of the <see cref="UmbracoAppAuthenticator"/> class.
/// </summary>
public UmbracoAppAuthenticator(IMemberService memberService)
{
_memberService = memberService;
}
/// <summary>
/// The unique provider name of ITwoFactorProvider implementation.
/// </summary>
/// <remarks>
/// This value will be saved in the database to connect the member with this ITwoFactorProvider.
/// </remarks>
public string ProviderName => Name;
/// <summary>
/// Returns the required data to setup this specific ITwoFactorProvider implementation. In this case it will contain the url to the QR-Code and the secret.
/// </summary>
/// <param name="userOrMemberKey">The key of the user or member</param>
/// <param name="secret">The secret that ensures only this user can connect to the authenticator app</param>
/// <returns>The required data to setup the authenticator app</returns>
public Task<object> GetSetupDataAsync(Guid userOrMemberKey, string secret)
{
var member = _memberService.GetByKey(userOrMemberKey);
var twoFactorAuthenticator = new TwoFactorAuthenticator();
SetupCode setupInfo = twoFactorAuthenticator.GenerateSetupCode("My application name", member.Username, secret, false);
return Task.FromResult<object>(new QrCodeSetupData()
{
SetupCode = setupInfo,
Secret = secret
});
}
/// <summary>
/// Validated the code and the secret of the user.
/// </summary>
public bool ValidateTwoFactorPIN(string secret, string code)
{
var twoFactorAuthenticator = new TwoFactorAuthenticator();
return twoFactorAuthenticator.ValidateTwoFactorPIN(secret, code);
}
/// <summary>
/// Validated the two factor setup
/// </summary>
/// <remarks>Called to confirm the setup of two factor on the user. In this case we confirm in the same way as we login by validating the PIN.</remarks>
public bool ValidateTwoFactorSetup(string secret, string token) => ValidateTwoFactorPIN(secret, token);
}
First, we create a model with the information required to set up the 2FA provider. Then we implement the ITwoFactorProvider with the use of the TwoFactorAuthenticator from the GoogleAuthenticator NuGet package.
Now we need to register the UmbracoAppAuthenticator implementation. This can be done on the IUmbracoBuilder in your startup or a composer.
UmbracoAppAuthenticatorComposer.cs
using Umbraco.Cms.Core.Composing;
using Umbraco.Cms.Core.DependencyInjection;
using Umbraco.Cms.Core.Security;
namespace My.Website;
public class UmbracoAppAuthenticatorComposer : IComposer
{
public void Compose(IUmbracoBuilder builder)
{
var identityBuilder = new MemberIdentityBuilder(builder.Services);
identityBuilder.AddTwoFactorProvider<UmbracoAppAuthenticator>(UmbracoAppAuthenticator.Name);
}
}
At this point, the 2FA is active, but no members have set up 2FA yet. The setup of 2FA depends on the type. In the case of App Authenticator, we will add the following to our view showing the edit profile of the member.
@using Umbraco.Cms.Core.Services
@using Umbraco.Cms.Web.Website.Controllers
@using Umbraco.Cms.Web.Website.Models
@using My.Website @* Or whatever your namespace with the QrCodeSetupData model is *@
@inject MemberModelBuilderFactory memberModelBuilderFactory
@inject ITwoFactorLoginService twoFactorLoginService
@{
// Build a profile model to edit
var profileModel = await memberModelBuilderFactory
.CreateProfileModel()
.BuildForCurrentMemberAsync();
// Show all two factor providers
var providerNames = twoFactorLoginService.GetAllProviderNames();
if (providerNames.Any())
{
<div asp-validation-summary="All" class="text-danger"></div>
foreach (var providerName in providerNames)
{
var setupData = await twoFactorLoginService.GetSetupInfoAsync(profileModel.Key, providerName);
if (setupData is null)
{
@using (Html.BeginUmbracoForm<UmbTwoFactorLoginController>(nameof(UmbTwoFactorLoginController.Disable)))
{
<input type="hidden" name="providerName" value="@providerName"/>
<button type="submit">Disable @providerName</button>
}
}
else if(setupData is QrCodeSetupData qrCodeSetupData)
{
@using (Html.BeginUmbracoForm<UmbTwoFactorLoginController>(nameof(UmbTwoFactorLoginController.ValidateAndSaveSetup)))
{
<h3>Setup @providerName</h3>
<img src="@qrCodeSetupData.SetupCode.QrCodeSetupImageUrl"/>
<p>Scan the code above with your authenticator app <br /> and enter the resulting code here to validate:</p>
<input type="hidden" name="providerName" value="@providerName" />
<input type="hidden" name="secret" value="@qrCodeSetupData.Secret" />
<input type="text" name="code" />
<button type="submit">Validate & save</button>
}
}
}
}
}
In this razor-code sample, we get the current member's unique key and list all registered ITwoFactorProvider implementations.
If the setupData is null for the specified providerName it means the provider is already set up. In this case, we show a disable button. Otherwise, we check the type and show the UI for how to set up the App Authenticator. We will show the QR Code and an input field to validate the code from the App Authenticator.
The last part required is to use the Login Partial View snippet.
Notification when 2FA is requested for a member
Two-factor authentication for Users
Umbraco controls how the UI is for user login and user edits, but will still need a view for configuring each 2FA provider.
Example implementation for Authenticator Apps for Users
TwoFactorAuthInfo.cs
using System.Runtime.Serialization;
using Google.Authenticator;
using Umbraco.Cms.Core.Models.Membership;
using Umbraco.Cms.Core.Security;
using Umbraco.Cms.Core.Services;
namespace My.Website;
[DataContract]
public class TwoFactorAuthInfo : ISetupTwoFactorModel
{
[DataMember(Name = "qrCodeSetupImageUrl")]
public string? QrCodeSetupImageUrl { get; set; }
[DataMember(Name = "secret")]
public string? Secret { get; set; }
}
/// <summary>
/// App Authenticator implementation of the ITwoFactorProvider
/// </summary>
public class UmbracoUserAppAuthenticator : ITwoFactorProvider
{
/// <summary>
/// The unique name of the ITwoFactorProvider. This is saved in a constant for reusability.
/// </summary>
public const string Name = "UmbracoUserAppAuthenticator";
private readonly IUserService _userService;
/// <summary>
/// Initializes a new instance of the <see cref="UmbracoUserAppAuthenticator"/> class.
/// </summary>
public UmbracoUserAppAuthenticator(IUserService userService)
{
_userService = userService;
}
/// <summary>
/// Gets the unique provider name of ITwoFactorProvider implementation.
/// </summary>
/// <remarks>
/// This value will be saved in the database to connect the member with this ITwoFactorProvider.
/// </remarks>
public string ProviderName => Name;
/// <summary>
/// Returns the required data to setup this specific ITwoFactorProvider implementation. In this case it will contain the url to the QR-Code and the secret.
/// </summary>
/// <param name="userOrMemberKey">The key of the user or member</param>
/// <param name="secret">The secret that ensures only this user can connect to the authenticator app</param>
/// <returns>The required data to setup the authenticator app</returns>
public Task<ISetupTwoFactorModel> GetSetupDataAsync(Guid userOrMemberKey, string secret)
{
IUser? user = _userService.GetByKey(userOrMemberKey);
ArgumentNullException.ThrowIfNull(user);
var twoFactorAuthenticator = new TwoFactorAuthenticator();
SetupCode setupInfo = twoFactorAuthenticator.GenerateSetupCode("My application name", user.Username, secret, false);
return Task.FromResult<ISetupTwoFactorModel>(new TwoFactorAuthInfo()
{
QrCodeSetupImageUrl = setupInfo.QrCodeSetupImageUrl,
Secret = secret
});
}
/// <summary>
/// Validated the code and the secret of the user.
/// </summary>
public bool ValidateTwoFactorPIN(string secret, string code)
{
var twoFactorAuthenticator = new TwoFactorAuthenticator();
return twoFactorAuthenticator.ValidateTwoFactorPIN(secret, code);
}
/// <summary>
/// Validated the two factor setup
/// </summary>
/// <remarks>Called to confirm the setup of two factor on the user. In this case we confirm in the same way as we login by validating the PIN.</remarks>
public bool ValidateTwoFactorSetup(string secret, string token) => ValidateTwoFactorPIN(secret, token);
}
First, we create a model with the information required to set up the 2FA provider. Then we implement the ITwoFactorProvider with the use of the TwoFactorAuthenticator from the GoogleAuthenticator NuGet package.
Now we need to register the UmbracoUserAppAuthenticator implementation and the view to show to set up this provider. This can be done on the IUmbracoBuilder in your startup or a composer.
UmbracoAppAuthenticatorComposer.cs
using Umbraco.Cms.Core.Composing;
using Umbraco.Cms.Core.Security;
namespace My.Website;
public class UmbracoAppAuthenticatorComposer : IComposer
{
public void Compose(IUmbracoBuilder builder)
{
var identityBuilder = new BackOfficeIdentityBuilder(builder.Services);
identityBuilder.AddTwoFactorProvider<UmbracoUserAppAuthenticator>(UmbracoUserAppAuthenticator.Name);
}
}
The last thing required is to register the provider in the Backoffice client so that the user can enable it. This can be done in a umbraco-package.json file.
At this point, the 2FA is active, but no users have set up 2FA yet.
Each user can now enable the configured 2fa providers on their user. This can be done from the user panel by clicking the user avatar.
When clicking the Configure Two-Factor button, a new panel is shown, listing all enabled two-factor providers.
When clicking Enable on one of these, the configured view for the specific provider will be shown
When the authenticator is enabled correctly, a disable button is shown instead.
To disable the two-factor authentication on your user, it is required to enter the verification code. Otherwise, admins are allowed to disable providers on other users.
If the code is correct, the provider is disabled.
Notification when 2FA is requested for a user
Login with 2FA enabled
When a user with 2FA enabled logs in, they will be presented with a screen to enter the verification code:
While the 2FA is enabled, the user will be presented with this screen after entering the username and password.
If the code is correct, the user will be logged in. If the code is incorrect, the user will be presented with an error message.
This screen is set up to work well with 2FA providers that require a one-time code to be entered. The code field follows best practices for accessibility in terms of labeling and autocompletion.
A user can have more than one 2FA provider activated simultaneously. In this case, the user will be presented with a dropdown to choose which provider to use before entering a code.
Customizing the 2FA experience
The 2FA experience can be customized in Umbraco. This can be done by creating a custom view for the activation screen and the login screen. This is useful if you have a 2FA provider that requires something else than a one-time code to be entered.
The following examples show how to customize the 2FA activation screen and the 2FA login screen.
The examples are using the @umbraco-cms/backoffice package to get access to the Umbraco backoffice components and services. This package is included in Umbraco and can be used to create custom elements that look and feel like the rest of the Umbraco backoffice.
Customizing the 2FA activation screen
The 2FA activation screen can be customized. This should be done if you have a 2FA provider that does not require a one-time code to be entered.
To customize the 2FA activation screen, you need to create a JavaScript module. The module should export a default custom element to be used in the activation screen. This module should be placed in the App_Plugins/TwoFactorProviders folder.
import { UserService } from '@umbraco-cms/backoffice/external/backend-api';
import { css, html } from '@umbraco-cms/backoffice/external/lit';
import { UmbLitElement } from '@umbraco-cms/backoffice/lit-element';
import { isApiError, tryExecuteAndNotify } from '@umbraco-cms/backoffice/resources';
import { UMB_NOTIFICATION_CONTEXT } from '@umbraco-cms/backoffice/notification';
import { UmbTextStyles } from '@umbraco-cms/backoffice/style';
export default class My2faActivationElement extends UmbLitElement {
static get properties() {
return {
providerName: { type: String },
displayName: { type: String },
callback: { type: Function },
close: { type: Function },
_loading: { type: Boolean, state: true, attribute: false },
_qrCodeSetupImageUrl: { type: String, state: true, attribute: false },
_buttonState: { type: String, state: true, attribute: false },
};
}
constructor() {
super();
this.consumeContext(UMB_NOTIFICATION_CONTEXT, (context) => {
this.notificationContext = context;
});
}
async firstUpdated() {
await this.#load();
this._loading = false;
}
async #load() {
if (!this.providerName) {
this.peek('Provider name is required', 'danger');
throw new Error('Provider name is required');
}
const { data: _data } = await tryExecuteAndNotify(
this,
UserService.getUserCurrent2FaByProviderName({ providerName: this.providerName }),
);
const data = _data;
if (!data) {
this.peek('No data returned', 'danger');
throw new Error('No data returned');
}
// Verify that there is a secret
if (!data.secret) {
this.peek('The provider did not return a secret.', 'danger');
throw new Error('No secret returned');
}
this._secret = data.secret;
this._qrCodeSetupImageUrl = data.qrCodeSetupImageUrl;
}
render() {
if (this._loading) {
return html`<uui-loader-bar></uui-loader-bar>`;
}
return html`
<uui-form>
<form id="authForm" name="authForm" @submit=${this.submit} novalidate>
<umb-body-layout headline=${this.displayName}>
<div id="main">
<uui-box .headline=${this.localize.term('member_2fa')}>
<div class="text-center">
<p>
<umb-localize key="user_2faQrCodeDescription">
Scan this QR code with your authenticator app to enable two-factor authentication
</umb-localize>
</p>
<img
id="qrCode"
src=${this._qrCodeSetupImageUrl}
alt=${this.localize.term('user_2faQrCodeAlt')}
title=${this.localize.term('user_2faQrCodeTitle')}
loading="eager" />
</div>
<uui-form-layout-item class="text-center">
<uui-label for="code" slot="label" required>
<umb-localize key="user_2faCodeInput"></umb-localize>
</uui-label>
<uui-input
id="code"
name="code"
type="text"
inputmode="numeric"
autocomplete="one-time-code"
required
required-message=${this.localize.term('general_required')}
label=${this.localize.term('user_2faCodeInputHelp')}
placeholder=${this.localize.term('user_2faCodeInputHelp')}></uui-input>
</uui-form-layout-item>
</uui-box>
</div>
<div slot="actions">
<uui-button
type="button"
look="secondary"
.label=${this.localize.term('general_close')}
@click=${this.close}>
${this.localize.term('general_close')}
</uui-button>
<uui-button
.state=${this._buttonState}
type="submit"
look="primary"
.label=${this.localize.term('buttons_save')}>
${this.localize.term('general_submit')}
</uui-button>
</div>
</umb-body-layout>
</form>
</uui-form>
`;
}
/**
* Show a peek notification with a message.
* @param message {String} The message to show.
* @param color {"positive" | "danger" | undefined} The color of the notification.
*/
peek(message, color) {
this.notificationContext.peek(color ?? 'positive', {
data: {
headline: this.localize.term('member_2fa'),
message,
},
});
}
/**
* Submit the form with the code and secret back to the opener.
* @param e {SubmitEvent} The submit event
*/
async submit(e) {
e.preventDefault();
const codeField = this.shadowRoot.getElementById('code');
codeField?.setCustomValidity('');
const form = e.target;
if (!form.checkValidity()) return;
const formData = new FormData(form);
const code = formData.get('code');
if (!code) return;
this._buttonState = 'waiting';
const { error } = await this.callback(this.providerName, code, this._secret);
if (!error) {
this.peek(this.localize.term('user_2faProviderIsEnabledMsg', this.displayName ?? this.providerName));
this._buttonState = 'success';
this.close();
} else {
this._buttonState = 'failed';
if (isApiError(error)) {
if (error.body?.operationStatus === 'InvalidCode') {
codeField?.setCustomValidity(this.localize.term('user_2faInvalidCode'));
codeField?.focus();
} else {
this.peek(
this.localize.term('user_2faProviderIsNotEnabledMsg', this.displayName ?? this.providerName),
'warning',
);
}
} else {
this.peek(error.message, 'warning');
}
}
}
static get styles() {
return [
UmbTextStyles,
css`
#authForm {
height: 100%;
}
#qrCode {
width: 100%;
aspect-ratio: 1;
}
#code {
width: 100%;
max-width: 300px;
}
.text-center {
text-align: center;
}
`,
];
}
}
customElements.define('my-2fa-activation', My2faActivationElement);
This module will show a QR code and an input field for the user to enter the code from the authenticator app. When the user submits the form, the code will be sent to the server to validate. If the code is correct, the provider will be enabled.
To replace the default activation screen with the custom view, you need to register the element in the umbraco-package.json file that you created before. The final form of the file should look like this:
{
"$schema": "../../umbraco-package-schema.json",
"name": "2fa providers",
"version": "1.0.0",
"extensions": [
{
"type": "mfaActivationProvider",
"alias": "UmbracoUserAppAuthenticator",
"name": "UmbracoUserAppAuthenticator",
"forProviderName": "UmbracoUserAppAuthenticator",
"element": "/App_Plugins/TwoFactorProviders/2fa-activation.js", // This line is the only change
"meta": {
"label": "Google Authenticator"
}
}
]
}
Customizing the login screen
The 2FA login screen can also be customized. This should be done if you have a 2FA provider that requires something else than a one-time code to be entered.
You should only customize the 2FA login screen in certain cases, for example:
If you have a provider that requires a non-numeric field or additional info.
If you have a provider that requires the user to scan a QR code, you should additionally show the QR code.
You need to create a JavaScript module that exports a default custom element to be used in the login screen. This module should be placed in the App_Plugins folder. The module should be registered using a composer.
You can use the following code as a starting point. This will give you a view looking like this, where the user can enter a code and click a button to verify the code. This is similar to the built-in view in Umbraco. In a real world scenario, you would probably want to authenticate the user in a different way.
The element registers two properties: providers and returnPath. These properties are used to render the view. The providers property is an array of strings, where each string is the name of a 2FA provider. The returnPath is the path to redirect to after a successful login. Both supplied by the login screen automatically.
We need to register the custom view using a composer. This can be done on the IUmbracoBuilder in your startup or a composer. In this case, we will add a composer to your project. This composer will overwrite the IBackOfficeTwoFactorOptions to use the custom view.
TwoFactorConfiguration.cs
using Umbraco.Cms.Core.Composing;
using Umbraco.Cms.Web.BackOffice.Security;
namespace My.Website;
/// <inheritdoc />
public class TwoFactorConfiguration : IBackOfficeTwoFactorOptions
{
/// <inheritdoc />
public string GetTwoFactorView(string username) => "/App_Plugins/TwoFactorProviders/Custom2faLogin.js";
}
public class TwoFactorConfigurationComposer : IComposer
{
public void Compose(IUmbracoBuilder builder)
{
builder.Services.AddSingleton<IBackOfficeTwoFactorOptions, TwoFactorConfiguration>();
}
}
When a 2FA login is requested for a member, the MemberTwoFactorRequestedNotification is published. This notification can also be used to send the member a one-time password via e-mail or phone. Even though these 2FA types are as App Authentication, it is still a massive improvement compared to no 2FA.
In the following example, we will use the . Despite the name, this package works for both Google and Microsoft authenticator apps. It can be used to generate the QR code needed to activate the app for the website.
When a 2FA login is requested for a user, the UserTwoFactorRequestedNotification is published. This notification can also be used to send the user a one-time password via e-mail or phone. Even though these 2FA types are as App Authentication, it is still a massive improvement compared to no 2FA.
The examples are using the library to create custom elements. This is the recommended way of creating custom elements in Umbraco. Lit is a light-weight library that augments the to provide a declarative, performant, and interoperable way to create web components.
They are written in vanilla JavaScript and C#, but the same principles can be applied to other languages. For more information about creating custom elements in Umbraco with a bundler and TypeScript, see the article.
If you need to authenticate the user in a different way than the default in Umbraco.
The following code is an example of a custom 2FA login screen using . This is the recommended way of creating a custom 2FA login screen. Lit is a light-weight library that augments the to provide a declarative, performant, and interoperable way to create web components.
