http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11590
--- Comment #6 from Galen Charlton <[email protected]> --- (In reply to Robin Sheat from comment #5) > (In reply to Kyle M Hall from comment #4) > > At this point I wonder why we still allow logins as the DB user. Wouldn't it > > be better to add a cli script to generate a first superlibrarian to log in > > with, and do away with db user logins altogether? > > Because it's really super handy as an administrator to be able to go in and > tweak or check some things for someone without having to have your own > account set up in their system. > > I do think that a large yellow warning ought to suffice, and this hasn't > seemed to have come up nearly as often since that was implemented. However, such issues have not been completely eliminated, either. It's not that big of a burden for folks who administer large numbers of Koha databases to simply create accounts from the CLI. I'm a +1 one for getting rid of the database user. If not that, at the very least we should stop exposing the database credentials that way and do something like putting in a new koha-conf.xml setting for username and (hashed!) password of a base superlibrarian "account". -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
