Command Side Authenticator (username and secret)

[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
  • Username
  • Password
  • JWT profile key
  • PAT
• When adding a new authenticator it is checked if that authentication method is allowed on the user schema
• RemoveAuthenticator: Removes an existing authenticator
  • Username
  • Password
  • JWT profile key
  • PAT

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]

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