-
Notifications
You must be signed in to change notification settings - Fork 2
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
[FEATURE] Account secrets #677
Labels
enhancement
New feature or request
Comments
roberlander2
added a commit
that referenced
this issue
Oct 3, 2023
…ded encryption, decryption utils [#677]
roberlander2
added a commit
that referenced
this issue
Oct 4, 2023
roberlander2
added a commit
that referenced
this issue
Oct 4, 2023
roberlander2
added a commit
that referenced
this issue
Oct 5, 2023
roberlander2
added a commit
that referenced
this issue
Oct 5, 2023
18 tasks
18 tasks
shurwit
pushed a commit
to rokmetro/core-building-block-fork
that referenced
this issue
Oct 7, 2023
* start implementing account secrets - added to core and API models, added encryption, decryption utils [rokwire#677] * implement service AES key management [rokwire#677] * update mock storage [rokwire#677] * add update secrets API, add decrypt secrets func to auth interface [rokwire#677] * add missing files * implement secrets decryption on get account and login [rokwire#677] * bug fixes and cleanup, add timestamp fields to key model (RSA-PSS parsing not working) [rokwire#677] * update changelog
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Currently we do not have a dedicated space to store user-specific secrets within an account.
Describe the solution you'd like
We should add a "secrets" field to the account that is similar to preferences in the sense that it can store any arbitrary data provided by the client. This data should be encrypted using the Core private key (same mechanism as access tokens in #627). This field will be decrypted and sent back with the user's account upon login and when they retrieve their account data. This field MUST NOT be exposed to anyone other than the currently authenticated user (ie. not exposed through admin APIs, public account data APIs... etc.)
The text was updated successfully, but these errors were encountered: