Skip to main content
Entire registers each plugin for you. Send your Entire contact the values below. You choose all of them except the slug, which Entire confirms, and the issuer and receipt audience, which follow from the slug for new registrations. If you have a legacy registration, use its assigned issuer and audience. To change your registered permissions later, ask your Entire contact. New installations accept the current set during consent. For an existing installation, a customer who manages the project must accept the updated permissions through the install consent flow. Registration alone does not grant them: a mint requesting an unaccepted permission returns 403 permission_not_accepted. A separate 409 coverage_changed means repository coverage or grants changed during the mint.

Make a key

Make a key with OpenSSL, and send the public half:
Keep plugin-key.pem in your secret store. Anyone who holds it can act as your plugin within its active installations and granted permissions. To rotate, send the new public key, deploy the new private key, then ask Entire to remove the old public key.
PEM keys are simplest. A JWKS URL suits you if you rotate keys often or keep keys in a KMS: your JWTs must then carry a kid header that names the key, and the SDK serves the JWKS for you with App.JWKSHandler when you configure Config.KeyID.