From 811b833dc254e2b18ca0deb2265615e4e3a509aa Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Fri, 26 Jan 2024 02:26:33 -0700 Subject: [PATCH] Update Configs & Servers/Linux/privacyIDEA.md --- Configs & Servers/Linux/privacyIDEA.md | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/Configs & Servers/Linux/privacyIDEA.md b/Configs & Servers/Linux/privacyIDEA.md index 059100d..a3ecd99 100644 --- a/Configs & Servers/Linux/privacyIDEA.md +++ b/Configs & Servers/Linux/privacyIDEA.md @@ -94,10 +94,20 @@ Now we need to create what is called a "**Realm**". Users need to be in realms | Realm Name | `Bunny-Lab` | | Resolver(s) | `BunnyLab-LDAP` | +## Configure Google Firebase for Push Notifications +Unfortunately, without recompiling the authenticator app (open-source) to handle a different provider, the default provider for Push Notifications specifically is Google Firebase. This will give you Google DUO functionality with push notifications for logon events, and the free "Spark" tier should be more than enough for 50 unique users or less. + +### Create a Push Notification Policy +Navigate to "**Config > Policies > Create New Policy**" + +- **Scope**: `Authentication` > "**push_allow_polling**" = `allow` +- **Scope**: `Enrollment` > "**push_firebase_configuration**" = `poll only` + ## Enrolling the First Token Navigate to "**Tokens > Enroll Token**" | **Field** | **Value** | | :--- | :--- | -| [x] Generate OTP Key on Server | `Bunny-Lab` | -| Resolver(s) | `BunnyLab-LDAP` | \ No newline at end of file +| Token Type | `PUSH: Send a Push Notification to a Smartphone` | +| Realm | `Bunny-Lab` | +| Username | `[256da6f8-9ddb-4ec5-9409-1a95fea27615] nicole.rappe (Nicole Rappe)` |