mirror of
https://github.com/0rangebananaspy/authelia.git
synced 2024-09-14 22:47:21 +07:00
683c4a70bf
* refactor(web): improve 2fa enrollment process This PR will change some of the wording and colours for the 2FA processes in order to provide more clarity and address some accessibility issues for end users. The following is a summary of the changes: * One-Time Password ⭢ Time-based One-Time Password * Security Key ⭢ Security Key - U2F ![Screenshot_2021-02-02-09-36-17](https://user-images.githubusercontent.com/3339418/107138185-17656100-6967-11eb-8fac-9e75c7a82d09.png) * QRCode ⭢ QR Code ![Screenshot_2021-02-07-05-07-25](https://user-images.githubusercontent.com/3339418/107138196-29df9a80-6967-11eb-811f-d77c9bb0159e.png) * `Not registered yet?` text to display `Lost device?` if a user has already registered a device of said type ![Screenshot_2021-02-02-10-24-54](https://user-images.githubusercontent.com/3339418/107138205-395ee380-6967-11eb-8826-83e1438dd146.png) * Change button and text colour in e-mails that Authelia generates * Change Authelia email footer to be more security conscious ![Screenshot_2021-02-07-04-51-40](https://user-images.githubusercontent.com/3339418/107138211-4085f180-6967-11eb-890b-9d931bd1ce76.png) The docs have also been updated to clarify the 2fa device enrollment limitation which only allows users to register one of each device type concurrently. Closes #1560.
60 lines
1.9 KiB
Markdown
60 lines
1.9 KiB
Markdown
---
|
|
layout: default
|
|
title: Push Notification
|
|
parent: Second Factor
|
|
nav_order: 3
|
|
grand_parent: Features
|
|
---
|
|
|
|
# Mobile Push Notification
|
|
|
|
Mobile push notifications is the new trendy second factor method. When second factor is requested
|
|
by Authelia, a notification is sent on your phone that you can either accept or deny.
|
|
|
|
<p align="center">
|
|
<img src="../../images/duo-push-1.jpg" width="200">
|
|
<img src="../../images/duo-push-2.png" width="200">
|
|
</p>
|
|
|
|
|
|
Authelia leverages [Duo] third party to provide this feature.
|
|
|
|
First, sign up on their website, log in, create a user account and attach it a mobile device.
|
|
Beware that the name of the user must match the name of the user in Authelia.
|
|
|
|
Then, in Duo interface, click on *Applications* and *Protect an Application*. Select the option
|
|
*Partner Auth API*. This will generate an integration key, a secret key and a hostname. You can
|
|
set the name of the application to **Authelia** and then you must add the generated information
|
|
to Authelia [configuration](../../deployment/index.md) as shown below:
|
|
|
|
duo_api:
|
|
hostname: api-123456789.example.com
|
|
integration_key: ABCDEF
|
|
secret_key: 1234567890abcdefghifjkl
|
|
|
|
Now that Authelia is configured, pass the first factor and select the Push notification
|
|
option.
|
|
|
|
<p align="center">
|
|
<img src="../../images/2FA-PUSH.png" width="400">
|
|
</p>
|
|
|
|
You should now receive a notification on your mobile phone with all the details
|
|
about the authentication request.
|
|
|
|
|
|
## Limitation
|
|
|
|
Users must be enrolled via the Duo Admin panel, they cannot enroll a device from
|
|
**Authelia** yet.
|
|
|
|
|
|
## FAQ
|
|
|
|
### Why don't I have access to the *Push Notification* option?
|
|
|
|
It's likely that you have not configured **Authelia** correctly. Please read this
|
|
documentation again and be sure you had a look at [config.template.yml](https://github.com/authelia/authelia/blob/master/config.template.yml).
|
|
|
|
[Duo]: https://duo.com/
|