@cbontemps Thanks for creating this issue. I like it! I think it makes sense to have a possibility to distinguish the events properly, as WebAuthn will be maintained in Keycloak for a long time and is included there by default. It'd be probably good to have even 'remove' events for that? @mposolda WDYT?

@mabartos Sorry for late answer. My vote is to rather have more generic event types like:
EventType=UPDATE_CREDENTIAL, details { credential_type=password }
or
EventType=UPDATE_CREDENTIAL, details { credential_type=webauthn }
or
EventType=UPDATE_CREDENTIAL, details { credential_type=webauthn-passwordless } .

Custom types for each credential doesn't work well with custom 2nd-factor credential types and will require some changes with each type introduced. But it is not a problem if credential has it's own way to add some additional details (Like EG. "attestation_statement" related details in the case of WebAuthn).

So ideal will be to rather remove types like UPDATE_PASSWORD or UPDATE_TOTP and replace them with something more generic. Same for REMOVE_TOTP for example

@mposolda Thanks for your comment. It makes sense.