-
-
Notifications
You must be signed in to change notification settings - Fork 16
Grant Access via WebApp #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
* created "create vault" component
until we solve server-side redirects to index.html
* Separate db of development/testing and production * Remove static uuid of admin in production but instead use a separate keycloak config file for development
If the user is still authenticated but the session token is expired, we get 401 status codes when executing requests. We need to refresh the token as long as we allowed until the user is logged out. For more details see https://stackoverflow.com/questions/43422542/keycloak-js-automatic-token-refesh
[ci skip]
| */ | ||
| export function uuid(): string { | ||
| return 'xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx'.replace(/[xy]/g, function (c) { | ||
| var r = Math.random() * 16 | 0, v = c == 'x' ? r : (r & 0x3 | 0x8); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
opt.semgrep.node_insecure_random_generator: crypto.pseudoRandomBytes()/Math.random() is a cryptographically weak random number generator.
(at-me in a reply with help or ignore)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sonatype-lift ignore
this uuid is just used to create vault ids, which aren't involved in anything security-related
This completes the unlock workflow by computing and storing a device-specific masterkey, i.e. the vault owner re-encrypts the masterkey using the public key of a certain trusted device.
The public key gets stored on first contact of the device (further device verification may be added later).
During unlock the device retrieves the key from via a callback URL which it will listen to on localhost (compatable to RFC 8252 section 7.3).