Repository navigation
Expose desktop credential identity in status - #321
Draft
Enksodsoon wants to merge 1 commit into
Draft
Enksodsoon wants to merge 1 commit into
Enksodsoon wants to merge 1 commit into
Conversation
This branch has not been deployed
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
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.
Desktop pairing currently returns an authenticated credential status without enough identity for Forge to scope the connection. This additive change returns the authorized default organization ID, authenticated user ID, and opaque credential ID from the existing credential-status route. It continues to omit the bearer token.
The pairing regression checks each identity value against persisted state and asserts that no access token is returned.
Validation on
e0cbd0e46bf0000fab89c77b760a1c73b902cd1a:libvips-42.dllis not installed on this host; the CI backend job installs the native runtime and passed.No existing Viewer account, Forge credential, or live slide data was changed. This PR remains a draft pending review; merge and deployment are still needed before live identity or delivery qualification.