If you try to register your circulation manager with the metadata wrangler, it's possible that the metadata wrangler will store a secret with your IntegrationClient but won't communicate the secret to you, due to a network error. In this case there is no way to register, since re-registration requires knowledge of the secret.

Amy and I have devised an alternative scheme which is backwards-compatible with the current scheme. In this scheme, an upgraded circulation manager can sign a JSON Web Token with their private key and send the JWT along with their registration request. The JWT proves ownership of the server even if the current secret isn't provided, which means the metadata wrangler can go ahead and issue a new secret.