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
Guest User Data Owner (amplify gen 2) #2489
Comments
Hey👋 thanks for raising this! I'm going to transfer this over to our API repository for better assistance 🙂 |
hi, any suggestions? I've been trying to find a way to set a custom owner field value for unauthorized users so only they can see records they have created for the duration of their active session. One approach I've looked into is using a lambda custom authorizer but have had no luck. I've been able to capture the identity pool session From the docs it doesn't appear possible to set an owner that isn't using userPools or oidc auth. And userPools don't appear to support unauthorized auth (which requires iam auth to be set). Is it possible to set unauthorized auth using userPool auth? Or is it perhaps possible to use oidc auth to configure a custom owner value without having to provide oidc details such as oidcIssuerUrl? |
We are using "anonymous" accounts. We create for our user a randomID@anon.com account in the userpool. |
👋 @domthomas1,
|
Hey 👋 , This issue is being closed due to inactivity. If you are still experiencing the same problem and need further assistance, please feel free to leave a comment. This will enable us to reopen the issue and provide you with the necessary support. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Environment information
Description
Allow guest/unauthenticated users to own data that they create so that only they can see/update the resources that they have created (within the current session), specifically within dynamodb records. I've seen there are ways to do this in gen 1 but it's not clear how to do this in gen 2. I've tried with the following model auth for example with no luck, using both iam and userPool auth mode:
.authorization(allow => [allow.owner(), allow.guest().to(['create'])])
.The text was updated successfully, but these errors were encountered: