Command Side Authenticator (factors)

[hifabienne]

As a ZITADEL Administrator I want to be able to create add/manage/remove all different kind of authenticators to my users in regards of having user schemas.

Acceptance Criteria

• Feature is behind a feature flag
• AddAuthenticator: Adds an authenticator
  • webAuthNKey
  • One time password Email
  • One time password SMS
  • Time based one time password
  • When adding a new authenticator it is checked if that authentication method is allowed on the user schema
• RemoveAuthenticator: Removes an existing authenticator
  • webAuthNKey
  • One time password Email
  • One time password SMS
  • Time based one time password

Questions to answer

Do we need to check if authentication method is allowed on the user schema or not?

Additional Information

Authenticators

• username: human readable identifier of the user
  • username
• password
• webAuthNKey
• one time password
  • email
  • phone
• time based one time password
• jwt profile key
• identity provider
• PAT
• FUTURE: recovery code

[hifabienne]

@stebenz @eliobischof Can you please estimate this issue?

[stebenz]

Estimation:

• authenticator events: 1d
• writemodels userschema allowed and exists: 0,5d
• command side: 0,5d
• unit tests for all types: 1d
• API definitions in oneof message: 0,5d
• integration tests: 1d

Summary: 4,5d

[hifabienne]

@eliobischof @stebenz As discussed I split the issue into 3 parts (username/secret, factors, identity providers), can you please estimate them?
#7896
#7897