Please remember to save the database later using the close database operation in order to persist any changes. If you use the open database operation, the database will be kept open and cached to the ntext so that further operations are faster. Older kdbx files are not supported! Please mind that kdbx version 4 files can be a bit slower. create, update or delete entries, list all entries or get a specific entryĬurrently it works best with kdbx version 3.1 but also kdbx version 4 (argon 2) is supported.a certain web service from within the app. Thus this node allows to hide credentials from the user that he should not have access to while he still should use e.g. Having further credentials within the kdbx-database, the flow may also use services the user would normally not have access to. We use it ourselves to authenticate users in a web-app (either by having one kdbx-file for each user and auth fails in case the kdbx-database could not be opened or by having one kdbx-file for all users and the credentials used for authorization are within this file). Always remember: You use it on your own risk! So use it with care! It is probably safer than using a badly secured database or a plain text file on disk. Therefore you should only use it in a trusted environment. ⚠️ Warning: ⚠️ Use this node with care! Opening a kdbx-file with this node exposes the contained credentials to the flow (and thus to the memory). This node lets you manage kdbx files (as used by KeePass and others). Node-Red nodes to work with keepass files.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |