Add passkey use to searchable attributes of user

[mooreds]

Add passkey use to searchable attributes of user

Problem

I want to be able to know how many folks are using passkeys on a FusionAuth instance.

Solution

Add passkey enabled as an indexed user attribute.

Alternatives/workarounds

Use the API to pull passkey data for each user, maintain it in another db.

Additional context

Came about when I tried to figure out how many folks are using passkeys on an instance I have access to and couldn't do so without writing a script.

Related issues:

• Add user link sources to the elasticsearch index #2791

Community guidelines

All issues filed in this repository must abide by the FusionAuth community guidelines.

How to vote

Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.

[robotdan]

This is doable in theory.

But in general, the search index (Elasticsarch or OpenSearch) schema mostly replicates the actual user. So adding attributes on the user index that don't exist on the user may not be ideal unless we want to break this pattern.

But I do think it would be valuable to index more "things" about a user.

For example, today to search on email using the query string DSL, you would ask for email:user@example.com - the object root is implied to be user.

I suppose ideally we would have made this user.email:user@exampe.com so we could then add other things to this query such as AND passkey:enabled (for example) - where passkey is another namespace.

[mooreds]

Yeah, per https://fusionauth.io/docs/reference/user-fields we have the following fields that extend beyond the user object that we index:

• registrations
• twoFactor info
• group memberships

I think registrations is nested, so maybe we need to use that for child objects? There are a number of other things it'd be great to know (passkeys, links).