Skip to content

OSS Blacklist Management

Control blacklist cleanup and keep OSS permissions when blacklisting a credential.

Overview

Blacklist handling used to work against integrators in two ways: entries were cleaned up automatically with no way to opt out, and blacklisting a credential destroyed its OSS permissions. Both behaviours changed.

Automatic cleanup of OSS blacklist entries is no longer applied unconditionally — it became a global configuration entry, so the decision belongs to the integrator. Blacklisting a credential no longer deletes its OSS permissions, and those permissions remain editable while the credential is blacklisted. A credential can therefore be blocked and later restored without having to rebuild its permissions.

Available since: Version 26.02 (June 2026 · API v34)

How to Use

Use Cases

  • Temporary blocking — blacklist a lost credential, then re-enable it once found, with its permissions intact
  • Controlled retention — keep blacklist entries for as long as the site requires instead of losing them to automatic cleanup
  • Prepared reinstatement — adjust the permissions of a blacklisted credential before putting it back in service

Updates

26.02 — June 2026

Initial Release

  • Automatic cleanup of OSS blacklist entries is now driven by a global configuration entry instead of always being applied
  • Blacklisting a credential no longer deletes its OSS permissions
  • OSS permissions can be edited for blacklisted credentials