stages/authenticator_validate: add ability to limit webauthn device types

[BeryJu]

Details

Similarly to #9114, allow restricting which types of WebAuthn devices can be used to authenticate. This is especially useful when users have multiple WebAuthn passkeys that might be required for different scenarios

---

Checklist

• Local tests pass (ak test authentik/)
• The code has been formatted (make lint-fix)

If an API change has been made

• The API schema has been updated (make gen-build)

If changes to the frontend have been made

• The code has been formatted (make web)

If applicable

• The documentation has been updated
• The documentation has been formatted (make website)

[netlify]

✅ Deploy Preview for authentik-docs canceled.

Name	Link
🔨 Latest commit	3e6467b
🔍 Latest deploy log	https://app.netlify.com/sites/authentik-docs/deploys/6617aa069e59ad000812c2d3

[netlify]

✅ Deploy Preview for authentik-storybook canceled.

Name	Link
🔨 Latest commit	3e6467b
🔍 Latest deploy log	https://app.netlify.com/sites/authentik-storybook/deploys/6617aa0697eb360008c1d667

[codecov]

Codecov Report

Attention: Patch coverage is 97.14286% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 92.41%. Comparing base (2698d90) to head (3e6467b).
Report is 7 commits behind head on main.

Files	Patch %	Lines
...thentik/stages/authenticator_validate/challenge.py	84.61%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9180      +/-   ##
==========================================
+ Coverage   92.40%   92.41%   +0.01%     
==========================================
  Files         646      646              
  Lines       31851    31910      +59     
==========================================
+ Hits        29431    29489      +58     
- Misses       2420     2421       +1     

Flag	Coverage Δ
e2e	50.41% <11.42%> (-0.06%)	⬇️
integration	26.31% <5.71%> (-0.04%)	⬇️
unit	89.81% <97.14%> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

authentik PR Installation instructions

Instructions for docker-compose

Add the following block to your .env file:

AUTHENTIK_IMAGE=ghcr.io/goauthentik/dev-server
AUTHENTIK_TAG=gh-ghcr.io/goauthentik/dev-server:gh-3e6467b8eb4136c8458406cd77245d3215397b85
AUTHENTIK_OUTPOSTS__CONTAINER_IMAGE_BASE=ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)s

For arm64, use these values:

AUTHENTIK_IMAGE=ghcr.io/goauthentik/dev-server
AUTHENTIK_TAG=gh-ghcr.io/goauthentik/dev-server:gh-3e6467b8eb4136c8458406cd77245d3215397b85-arm64
AUTHENTIK_OUTPOSTS__CONTAINER_IMAGE_BASE=ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)s

Afterwards, run the upgrade commands from the latest release notes.

Instructions for Kubernetes

Add the following block to your values.yml file:

authentik:
    outposts:
        container_image_base: ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)s
image:
    repository: ghcr.io/goauthentik/dev-server
    tag: gh-ghcr.io/goauthentik/dev-server:gh-3e6467b8eb4136c8458406cd77245d3215397b85

For arm64, use these values:

authentik:
    outposts:
        container_image_base: ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)s
image:
    repository: ghcr.io/goauthentik/dev-server
    tag: gh-ghcr.io/goauthentik/dev-server:gh-3e6467b8eb4136c8458406cd77245d3215397b85-arm64

Afterwards, run the upgrade commands from the latest release notes.