mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-13 03:13:58 +03:00
Login by name #1230
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ezzra on GitHub (Jun 19, 2019).
I don't know if this has already been discussed anywhere here, but is there a reason why one has to login by email and not by name? Many tools use the same form field ("put in your name or your email address") which is much more convenient.
@ssddanbrown commented on GitHub (Jun 22, 2019):
Yeah, There are a few reasons:
To be honest, I can't think of any platforms I use where you can use name to login. Many allow login via username or email but BookStack does not really store a username (Unless LDAP is in use).
@hambern commented on GitHub (Oct 28, 2019):
I understand the reasoning here. But I'm a teacher and want to publish materials for them om my wiki. Just for them, not public, protected by a password. So I want to create a "student" account and have them login with the name "student" with a password.
And I don't want to store every students email-addresses because of GDPR
@rmoe88 commented on GitHub (Apr 17, 2020):
I would like to bump this feature request. For the home-user it would be very helpful, so I don't have to have the family have to remember multiple login methods for the local network services I have going, and they could just remember their one user-pass.
@NextBlaubeere commented on GitHub (Oct 12, 2020):
+1 for a simple username + password login.
@johnroyer commented on GitHub (Jan 9, 2021):
I hope display name can be unique. Some feature will need unique name.
For example, somebody need to notify the page editor
JohnDoe, they might type@JohnDoein comment (issue #953). But if display name is not unique, notification can not be done. More then one person will be notified.@ezzra commented on GitHub (Jan 9, 2021):
I dont know @ssddanbrown `s plans here, but there are solutions in other tools, where you can have a unique username and a display name and you can use both to @mention someone (using display name will be converted to username in a small menu, like here in github by the way)
@horstepipe commented on GitHub (Oct 16, 2021):
I‘d like to see this, too.
Are there any workarounds to achieve that? I just want to host a simple wiki with predefined usernames and passwords which I give to my users, so there is no mail validity needed at all.
When using ldap there still is a need of an email address I guess?
@horstepipe commented on GitHub (Oct 19, 2021):
okay it is working with openldap, so that's a workable workaround.
@flemmingss commented on GitHub (Apr 12, 2023):
Old topic, but I support adding a way to just use "username".
I use my server to personal notes and have no mail configuration set up (so reset password or notifications to mail ect don't work here anyway "by design")
Also, some ideas and stuff:
Why not have a optinal email field and username field in the profile? Then I can login with both "user1" or "user1@random.domain".
Idea:
@ssddanbrown commented on GitHub (Apr 12, 2023):
I've published a hack to add this kind of functionality within the hacks site:
https://www.bookstackapp.com/hacks/username-login/
This can be used to essentially get what's been asked for here. The logic is quite simple so could be tweaked to your own requirements.
Otherwise, I'm going to close this off since it's not something I'd look to support an option for (And it would really need to be an option for forward-compatibility reasons), while being something I'm personally not fond of in terms of UX (At least when talking about dual-purpose email/username inputs), and since this has relatively low demand for a change to auth while having a possible workaround.