Add "uniqueId" parameter to Google Authenticator .proto schema#1682
Open
hicallmeal wants to merge 1 commit intobeemdevelopment:masterfrom
Open
Add "uniqueId" parameter to Google Authenticator .proto schema#1682hicallmeal wants to merge 1 commit intobeemdevelopment:masterfrom
hicallmeal wants to merge 1 commit intobeemdevelopment:masterfrom
Conversation
Per beemdevelopment#1681, this additional otpParameter sometimes appears in Google Authenticator exports. Its purpose is likely to help avoid sync conflicts.
Author
|
It just occurred to me that it may be an I read on field cardinality but it's not actually clear to me that a non- I've long assumed many of the parameters (alg, digits, etc) aren't always present in exports and those aren't |
Callie84
approved these changes
Sep 9, 2025
Callie84
approved these changes
Sep 9, 2025
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.
Opened for #1681.
As mentioned in the issue, this makes no material difference to Aegis's ability to import Google Authenticator data, however, you may wish to include it regardless.
No problem if rejected, given the above.