ShareShield 4.0.5: built-in apps, managed like every other app
ShareShield 4.0.5 manages built-in OAuth apps, such as the browser extension, in the same place as every other app, and checks the addresses apps return to more strictly.
ShareShield 4.0.5 is out. It’s a small release, mostly behind the scenes, and there’s nothing you need to do.
Built-in apps
4.0.4 brought OAuth apps, and with them one app built into ShareShield: the coming browser extension. Its settings, such as which addresses it may return to after sign-in, used to be fixed in ShareShield’s server settings. Built-in apps are now kept in the same place as the apps organisations register, and we manage them there.
That means we can set the extension up for each browser store as it’s published, without changing or restarting ShareShield.
For your organisation nothing changes. Under Dashboard → OAuth apps, built-in apps are marked Built-in. Owners and admins can see their settings and who has connected them, and disconnect anyone, but can’t edit them.
Stricter redirect checks
After someone approves an app, ShareShield sends them back to one of the addresses registered for it. Those addresses are now checked each time they’re used. A stored address that’s malformed, or that ShareShield wouldn’t accept when an app is registered, is never used, and sign-in stops with an error instead.
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.
