News

ShareShield 4.0.4: tighter single sign-on and OAuth for apps

ShareShield 4.0.4 limits how long an SSO sign-in lasts, keeps removed members out, lets policies switch off open notifications, and adds OAuth 2.1 sign-in for apps.

On this page
  1. Single sign-on
  2. Policies and the organisation
  3. OAuth 2.1 for apps
  4. Also fixed

ShareShield 4.0.4 is out. Most of it tightens single sign-on, and it adds OAuth 2.1, so apps can act for you without an API key. There’s nothing you need to do.

Single sign-on

  • SSO sign-ins have a maximum lifetime. An SSO sign-in now lasts at most 24 hours, however active you are. Then ShareShield checks with your identity provider again and brings you back to the page you were on. If you’re still signed in there, for example to Microsoft Entra ID through Windows, that happens without a prompt. Owners can set a shorter limit, from 1 hour, in the SSO settings.
  • Removed members stay removed. Removing someone from your organisation now stops SSO sign-in and domain auto-join from adding them back. If you want them back, invite them again.
  • Sign-in uses only the checked endpoints. When an owner saves the SSO settings, ShareShield checks the identity provider’s endpoints and keeps them. If they change later, SSO sign-in is refused until an owner saves the settings again.
  • Domain verification asks the domain’s own name servers for its TXT record. A record you’ve just published is seen straight away, and a stale or forged cached answer can’t verify a domain.

Policies and the organisation

  • Policies can switch “Notify me” off. On the Policies page, choose whether members decide, whether it’s on by default, or whether it’s always off. When it’s off, the send form locks it off and API requests that ask for it are refused.
  • Owners can rename the organisation on the Organization page. Admins can now open that page too, and see the name.
  • Sign-in rate limits hold under load. Many sign-in attempts at once can no longer slip past a limit before they’re counted.

OAuth 2.1 for apps

An API key acts as the person who made it. An app that acts for other people can now sign them in with OAuth 2.1 instead. Each person signs in to ShareShield, chooses the organisation and approves what the app may do. The app then works through API v2 with that person’s access, and never more than their current role allows.

  • Owners and admins register their organisation’s apps under Dashboard → OAuth apps, and can see and revoke who has authorised each one.
  • Everyone can see and revoke the apps they’ve approved under Profile → Authorized apps.
  • OAuth apps are on every plan.

This is also how the coming ShareShield browser extension signs in. It’s built into ShareShield, so anyone can connect it without an admin setting it up.

Developers: OAuth apps explains how to register an app and sign people in, and the API reference in the app has the full detail.

Also fixed

  • Phones: the dashboard header and the API reference no longer scroll sideways on narrow screens.
  • Billing: a subscription cancelled in the billing portal now shows as ending at the end of the period through the API, as it already did on the Billing page.

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.

All news