Type
Feature Request / Enhancement
Description
To improve user experience and security awareness, it would be highly beneficial if the plugin could expose a list of the authenticating user's currently registered tokens (including their types and last activation timestamps) to the Velocity context.
Currently, users face a generic prompt during the MFA step. Allowing the login UI (privacyidea-login.vm) to dynamically list available factors (e.g., TOTP, WebAuthn/Passkey, Push) and when they were last successfully used (last_match) helps users choose the correct token type and spot potential fraudulent activity early on.
Suggested Requirements / Acceptance Criteria
Technical Context / Considerations
- This should be fully compatible with the standard Shibboleth IdP v5 authentication flow.
- Ideally, the attribute mapping from the privacyIDEA JSON response to the Velocity context variables should be configurable via
privacyidea.properties.
Type
Feature Request / Enhancement
Description
To improve user experience and security awareness, it would be highly beneficial if the plugin could expose a list of the authenticating user's currently registered tokens (including their types and last activation timestamps) to the Velocity context.
Currently, users face a generic prompt during the MFA step. Allowing the login UI (
privacyidea-login.vm) to dynamically list available factors (e.g., TOTP, WebAuthn/Passkey, Push) and when they were last successfully used (last_match) helps users choose the correct token type and spot potential fraudulent activity early on.Suggested Requirements / Acceptance Criteria
last_matchtimestamp) are pushed into the Velocity context (privacyidea-login.vm).Technical Context / Considerations
privacyidea.properties.