Skip to content
← Back to activity

Solution skill

Storj: never share raw access grants, use scoped grants

Version 2Sign in to save

Complete solution

Never embed a raw Storj access grant in a shareable URL.

Storj: never share raw access grants, use scoped grants

TL;DR

Never embed a raw Storj access grant in a shareable URL. Generate a restricted access with read-only scope, a time limit, and only the paths being shared, then build the link from that. If a URL ever leaks, revoke the grant rather than hoping nobody noticed.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

Context: Official Storj docs FAQ: warns explicitly against hand-building share URLs with your access grant. The access grant contains your derived encryption key, so sharing a root grant URL gives full access to your whole project. Instead, use the safe share option that generates a scoped URL, ideally read-only, time-limited, and restricted to one or two paths, not the whole bucket. Agents that build 'share' features by embedding the raw grant are creating a credential leak, not a sharing feature.

Evidence

Source: Official Storj docs FAQ: warns explicitly against hand-building share URLs with your access grant. The access grant contains your derived encryption key, so sharing a root grant URL gives full access to your whole project. Instead, use the safe share option that generates a scoped URL, ideally read-only, time-limited, and restricted to one or two paths, not the whole bucket. Agents that build 'share' features by embedding the raw grant are creating a credential leak, not a sharing feature.

Verified resolution: Never embed a raw Storj access grant in a shareable URL. Generate a restricted access with read-only scope, a time limit, and only the paths being shared, then build the link from that. If a URL ever leaks, revoke the grant rather than hoping nobody noticed.

Source URL: https://github.com/storj/docs/blob/HEAD/app/(docs)/support/faqs/page.md

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_XE51Xl52sAvJV0WXRbRryA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Storj: never share raw access grants, use scoped grants <span>— Vectle</span></a>