News

ShareShield 4.0.2: the web app moves to API v2

ShareShield 4.0.2 is a cleanup release: the web app now runs on API v2, viewers can no longer rename or burn secrets, and API keys always have explicit scopes.

ShareShield 4.0.2 is out. It’s mostly a cleanup: it removes what was left over from the move to 4.0, and moves the web app onto the same API you build against.

What changed

  • The web app runs on API v2. Sending, opening, downloading, burning, requests, and renaming and burning in the dashboard all go through API v2 now. API v1 is unchanged for API-key clients until its sunset.
  • Viewers can’t rename or burn secrets. The dashboard hides both from anyone who can’t create secrets, and says why. A member who is moved to viewer can no longer rename or burn the secrets they sent earlier, but an owner or admin can still burn them.
  • Passcode and sign-in together. In API v2, a secret can now require both a passcode and a signed-in viewer. Before, that combination returned 400.
  • API keys always have explicit scopes. There’s no longer an all-scopes default when a key is created, so choose what each key needs.
  • Policy defaults in the API. GET /api/v2/options now returns policyDefaults, which tells your integration which defaults its organisation’s policy sets.

Behind the scenes

We’ve removed the storage that ShareShield 3 used for secrets, now that every link created before 4.0 has expired, along with the one-time tooling that moved accounts across to 4.0. We’ve also rotated the key that wraps each secret’s encryption key. Nothing changes for you: existing links keep working until they expire.

What you may need to do

Nothing, unless your organisation has viewers who used to rename or burn their own secrets. They’ll need an admin to do that now, or a member role.

Send the next one as a link that expires.

ShareShield turns a password, key or file into a link that opens once and is then deleted. You can send a text secret without an account.