During the initial admin setup I am forced to use (quite arbitrary) requirements for most of the fields.
Personally I intend to use OIDC for users and admins later so these might not be an issue then but I prefer to set up an initial admin that is local to the service as a fallback. Requiring an email for something intended to be local is bizarre.
While I think having the requirements on by default isn't a problem it would be nice to allow disabling the forced email field, username and password length requirements. At least allow it via the compose as a variable that can be turned back on later but configuration in the admin panel would be nice, like for changing the length or complexity requirement for the password.
During the initial admin setup I am forced to use (quite arbitrary) requirements for most of the fields.
Personally I intend to use OIDC for users and admins later so these might not be an issue then but I prefer to set up an initial admin that is local to the service as a fallback. Requiring an email for something intended to be local is bizarre.
While I think having the requirements on by default isn't a problem it would be nice to allow disabling the forced email field, username and password length requirements. At least allow it via the compose as a variable that can be turned back on later but configuration in the admin panel would be nice, like for changing the length or complexity requirement for the password.