mirror of
https://github.com/opensolutions/ViMbAdmin.git
synced 2026-04-26 00:36:00 +03:00
[GH-ISSUE #184] [Security Suggestion] Password field and initial password #145
Labels
No labels
bug
feature
feature
improvement
improvement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ViMbAdmin-opensolutions#145
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @Sebbo94BY on GitHub (Apr 16, 2016).
Original GitHub issue: https://github.com/opensolutions/ViMbAdmin/issues/184
Currently, you can set a password and it will be displayed in clear-text instead of censored. Please change the input field to password instead of text and add a second one to validate the entered password.
If needed, you may can add a "View password" button, which temporarly changes the password-field to a text-field.
If the user uses the "create a random password" button, it should be automatically set to both input fields.
Anyway: In my opinion it's a no go, to send out the set password in clear-text via email to the user.
I would prefer, that the password isn't sent out, if at creation of the mailbox an individual password was set. If it's a random password, it should be send seperatly in a second email and/or the user has to change it immediately after the first login. This action needs to be forced at login.
@Sebbo94BY commented on GitHub (Aug 26, 2016):
Any news regarding this topic?
@barryo commented on GitHub (Aug 29, 2016):
Haven't had a chance to look at this. A PR would be welcome to move things along.
@Sebbo94BY commented on GitHub (Aug 29, 2016):
Sorry, didn't get that. What would be welcome?
@barryo commented on GitHub (Aug 29, 2016):
PR => Pull Request (i.e. code)
@Sebbo94BY commented on GitHub (Aug 29, 2016):
Ah, ok. Yes, when I can find some time at weekend, I'll try to figure out a solution.
@Sebbo94BY commented on GitHub (May 17, 2020):
@barryo has this been changed?
@barryo commented on GitHub (May 18, 2020):
No @Sebi94nbg - just closing it for 'timeout' - dates from 2016 😉
@barryo commented on GitHub (May 18, 2020):
(still happy to look at a PR of course)