Skip to content
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

Assess implications for Airtable's change of attachment URL functionality #29

Open
janbaykara opened this issue Aug 16, 2022 · 1 comment
Labels
question Further information is requested

Comments

@janbaykara
Copy link
Member

Relevant support article on the change: https://support.airtable.com/hc/en-us/articles/4852449595671-Changes-to-Airtable-attachments

In an effort to increase attachment security, on November 8th, 2022 Airtable will be incorporating expiring links functionality. That means when you share attachments stored in Airtable via URL with external colleagues the link you provide them will expire after a couple of hours. Read on to learn more about how to prepare for the upcoming changes.

Currently, Airtable attachments include a static URL where the attachment can be publicly accessed via a web browser. These links never expire and could be accessed by anyone who obtains the attachment’s link. This presents a potential security risk for any files that contain sensitive information. For that reason, we are introducing expiring public-accessible attachment links.

I think we're using attachment URLs for action files, which might mean they expire. On the other hand, we're also using next/image, which does some image caching. Do the two cancel each other out, or do we need to figure out a solution?

@janbaykara
Copy link
Member Author

Also discussing this over at another project which uses this codebase: gameworkersolidarity/website#39

@janbaykara janbaykara added the question Further information is requested label Aug 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant