Repository navigation
Reprint public key management - #10
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Exports are now verified by Reprint's RequestAuthenticator, which accepts the installed key or the shared secret, whichever the host supports. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The screen gets a public key textarea and a table with the enrolled key's id and a Remove button, modelled on the Reprint Server plugin. Remove secret now removes only the secret, so each credential is managed on its own. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Export errors now carry Reprint's reason code, and not_configured answers with a 503, as the Reprint Server plugin does. Without the reason, the client blamed an outdated plugin for an unknown key. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reprint is moving to a public-key auth model instead of using shared HMAC secrets. This PR updates the Reprint dependency and adds a few key tools for managing public keys through the plugin:
/wpcom-migration/v1/reprint/install-public-keyAPI endpoint. As the name suggests, it inserts a new public key. Authentication is the same as for the/wpcom-migration/v1/reprint/rotate-export-secretendpoint, i.e., the request needs to be signed with a Jetpack token or a local user credential (e.g., an application password) by a user with anadministratorrole.