Repository navigation
feat(gateway): test a key against the gateway's current one in Settings › Gateway access - #449
Merged
Merged
Conversation
…gs › Gateway access A Test button beside Apply checks the key in the field against the saved one, saving nothing. It answers that's the current key, that isn't, or that no key is saved. It's operator only (CheckApiKeyAsync); the desktop's own engine has no key. Closes #447
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.
Closes #447.
The gateway keeps only a hash of its API key, so it can't show the key. This adds a way to check a key you have, from a desktop app's settings or a password manager.
IEngineService.CheckApiKeyAsync(key)answersApiKeyCheck: Accepted, Refused or None.AllowSettingsChangessays.gateway.api-key-not-here.Verified