mirror of
https://github.com/appy-one/acebase.git
synced 2026-05-25 06:02:14 -06:00
[GH-ISSUE #60] Request: Example or test file of using acebase with username + salt + hash? #43
Labels
No labels
IndexedDB
browser
bug
dependencies
documentation
duplicate
enhancement
feature request
indexes
indexes
invalid
pull-request
query
question
transaction logging
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/acebase#43
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 @qpwo on GitHub (Jan 5, 2022).
Original GitHub issue: https://github.com/appy-one/acebase/issues/60
I think I know how to store the passwords but a good example would put me at ease. I searched password, salt, & hash in the repo and couldn't find anything.
Here's an example typescript/express/node auth server without the db, if that helps: https://gist.github.com/qpwo/4b2ae3aaaf222d099b34898152118c43
Or if you don't have time yourself I could PR a new test case
@appy-one commented on GitHub (Jan 5, 2022):
You don't have to store passwords or salts or hashes anywhere in your database. You are probably searching for the
authfunctionality built into AcebaseServer and AceBaseClient. User management is all built into the client and server code, you won't have to worry about authentication!@qpwo commented on GitHub (Jan 5, 2022):
Holy crap how did i miss that. Acebase really has the best of everything