Application authentication methods
Record how your users log into each application and see, thanks to the browser extension, which methods they actually use
The Authentication section of an application's page describes how your users log into it: password, SSO, passkey… You record one or more methods there, and Kabeen shows for each one the share of users who actually use it, based on the logins observed by the browser extension.
This information helps you assess each application's security level and your users' login experience: an application still reachable with a plain password, an SSO that few people use, logins without a second factor.
Where to find the Authentication section
Open the application's page, then the Architecture tab. The Authentication section shows one card per method. If no method is recorded, it says "No authentication method set".
The authentication recorded before the 17 November 2026 release has become each application's first method.
Methods and their details
| Method | What you specify |
|---|---|
| Password | The Protocol: HTTPS, Kerberos, LDAP or Other |
| SSO | The Provider: Microsoft, Google, Okta, AD FS, ProConnect, FranceConnect… or Other |
| Passkey | — |
| One-time code | — |
| Magic link | — |
For each method, you can also set the Secondary factor it asks for: None, Biometry, One-time password, Smart card, Certificate, FIDO U2F, PIN or Authentication application.
A method can only be recorded once per application. An SSO can however be recorded once per provider, for example Microsoft and Google for an application that accepts both.
Recording a method
- In the Authentication section, click + (or Add an authentication method if none is recorded yet).
- Choose the Method.
- Depending on the method, choose the Provider (SSO) or the Protocol (password), then the Secondary factor.
- Click Add.
To edit a method, click its card. The window also offers Delete this method.
The section is visible to every member who can read the application. Adding, editing or deleting a method requires being able to edit the application, through their role or a specific right. See Roles and permissions.
What the observed logins show
When the browser extension is deployed, each card shows a gauge: the share of users who log in with this method, among those whose logins to the application the extension observed over the last 3 months.
Hovering over the card shows the details:
| Information | Meaning |
|---|---|
| Users and Occurrences | How many users used the method, and how many logins it accounts for |
| Main provider | The most used provider, for an SSO |
| Second factor requested | The share of logins that asked for a second factor, and which one |
| Password manager | The share of logins where the password was filled in automatically |
| Session already open | The share of logins made without typing anything, thanks to an existing session |
| Median login time | The median time between the start and the end of the login |
If the extension observed no login to the application over that period, the card says so: "No login seen by the extension over the last 3 months".
Methods detected by the extension
A method your users rely on but that isn't recorded yet still shows, marked Detected by the extension. Click its card to see its details, read-only: a detected method can't be edited or deleted. To keep it in the application's description, add it yourself with +.
It often points to a gap between what was planned and what actually happens: for example, a password login left open next to the SSO.
Filtering and exporting
In the application list, the archives and the diagrams, the Authentication filter works on the recorded methods: Method, SSO provider, Protocol and Secondary factor. For example, you can find in two clicks the applications that still accept a password without a secondary factor.
Application exports also list their authentication methods.
In custom dashboards
Custom dashboards offer measures based on the observed logins (logins, users who logged in, SSO rate, MFA rate, logins without MFA) and breakdowns by recorded method. See Custom dashboards.