-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Parse S3 File Access with No Credentials #832
Comments
@nkranes I think it is. I noticed that too. Just out of curiosity where did you set the credentials for the S3Adaptor?. Im using a config JSON file to run with pm2 but cant seem to configure it now with 2.1.4. |
@Cliffordwh for now we don't have a support for those env variables :( |
@flovilmart OOOo makes sense. Where could i then hard code a quick fix to get it to work. in 2.1.3 i managed to just code it into |
I'm on it! |
@Cliffordwh I don't use env vars. My config looks like:
|
@nkranes Thanks. Was just informed it wont work yet with env. |
So @flovilmart , is open S3 file access through Parse intentionally open? |
@Cliffordwh - yeah, @flovilmart types faster than I do. :) |
@flovilmart Thanks for that. So is it safe to run Cause that didnt work for me/. |
Hat would need to be the full path to the module I believe |
like parse-server/Adapters/Files/S3Adapter |
If I understand the issue correctly, this is the intended behavior of files. If you have a file URL, you have access to the file. This is also how it worked on Parse.com. |
@gfosco so there is no real difference between directAccess true or false. if the file url is known, the file is accessible. i am right? |
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!
-[X] You've met the prerequisites.
-[X] You're running the latest version of Parse Server.
-[X] You've searched through existing issues. Chances are that your issue has been reported or resolved before.
Environment Setup
AWS, Parse 2.1.4, using S3 File Adapter
Steps to reproduce
Upload file through parse. Url is returned.
Hit new file through Parse (directAccess: false) with no credentials and it returns properly. I believe in previous versions this request required Parse credentials. Is this by design?
Logs/Trace
The text was updated successfully, but these errors were encountered: