You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having a password validation in the client does not look like a good idea.
I have a harbor server connected to an LDAP which has it set of password requirements, just let the server handle the authetication instead of doing a client enforcement on how your password needs to be. My users can login due to how the code is written.
The validation can be there for creating a user but not for login.
Remove the password validation from pkg/views/login/create.go.
diff --git a/pkg/views/login/create.go b/pkg/views/login/create.go
index ad65352..aae78f7 100644
--- a/pkg/views/login/create.go+++ b/pkg/views/login/create.go@@ -58,9 +58,6 @@ func CreateView(loginView *LoginView) {
if strings.TrimSpace(str) == "" {
return errors.New("password cannot be empty or only spaces")
}
- if err := utils.ValidatePassword(str); err != nil {- return err- }
return nil
}),
huh.NewInput().
The text was updated successfully, but these errors were encountered:
Having a password validation in the client does not look like a good idea.
I have a harbor server connected to an LDAP which has it set of password requirements, just let the server handle the authetication instead of doing a client enforcement on how your password needs to be. My users can login due to how the code is written.
The validation can be there for creating a user but not for login.
Remove the password validation from pkg/views/login/create.go.
The text was updated successfully, but these errors were encountered: