add impersonation to user, and metadata to user and org #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The User now has an "impersonator_user_id" field. This is the UUID of the other user that is impersonating this user. It will be None if impersonation is not happening (which it normally isn't). The User objects also have a "metadata" field, which is private, user-specific metadata which can be set via the regular update_metadata endpoint. The user will never see or use this metadata, it's just for the PropelAuth customer. The Org objects have an "org_metadata" field. Much like user metadata, this is a private field. The metadata objects are simple hashes with a string key and any JSON object for the value.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
andrew-propelauth
requested changes
Apr 13, 2023
| #[serde(rename = "legacy_user_id", skip_serializing_if = "Option::is_none")] | ||
| pub legacy_user_id: Option<String>, | ||
| #[serde(rename = "impersonated_user_id", skip_serializing_if = "Option::is_none")] | ||
| pub impersonated_user_id: Option<String>, |
Contributor
There was a problem hiding this comment.
I don't think this field exists for UserMetadata, just for the User since that's in the access token.
andrew-propelauth
approved these changes
Apr 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The User now has an "impersonator_user_id" field. This is the UUID of the other user that is impersonating this user. It will be None if impersonation is not happening (which it normally isn't).
The User objects also have a "metadata" field, which is private, user-specific metadata which can be set via the regular update_metadata endpoint. The user will never see or use this metadata, it's just for the PropelAuth customer.
The Org objects have an "org_metadata" field. Much like user metadata, this is a private field.
The metadata objects are simple hashes with a string key and any JSON object for the value.