Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

675: Add support for static qr codes in frontend #747

Merged
merged 2 commits into from
Jan 26, 2023

Conversation

sarahsporck
Copy link
Contributor

No description provided.

Copy link
Member

@michael-markl michael-markl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is probably missing in the issue description, but I think we agreed on the following:
In the case, a static card is being verified, the user (the verifier) should be asked "more thoroughly" to check the personalausweis (for example, once the server has verified the static card, a checkbox labeled "Ich habe die Daten mit einem amtlichen Lichtbildausweis abgeglichen" should be shown, and only once this checkbox is checked, it should show "Nürnberg-Pass ist gültig".)
Should we do this in another issue? I guess it shouldn't block this PR.

[ I haven't tested the PR yet; only Code Review ]

@@ -42,6 +70,12 @@ void _assertConsistentDynamicVerifyCode(DynamicVerifyCode verifyCode) {
}
}

void _assertConsistentStaticVerifyCode(StaticVerifyCode verifyCode) {
if (!verifyCode.hasPepper()) {
throw QrCodeFieldMissingException("hashSecretBase64");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
throw QrCodeFieldMissingException("hashSecretBase64");
throw QrCodeFieldMissingException("pepper");

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So is it called pepper when there is no totpSecret and hashSecretBase64 when there is a totpSecret?

Copy link
Member

@michael-markl michael-markl Jan 25, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no, it is always called papper :) We renamed it a few weeks ago from hashSecret to pepper, but there might be a few occurences left to fix

@sarahsporck sarahsporck force-pushed the 675-support-static-qr-codes branch 2 times, most recently from 6a20981 to ea3c09a Compare January 25, 2023 09:06
@sarahsporck
Copy link
Contributor Author

I would prefer to add the checkbox in a separate ticket, as I am really not familiar with how to build nice flutter ui and someone else can do this in half the time I'd need. Therefore I'll create an issue for this.

@sarahsporck sarahsporck force-pushed the 675-support-static-qr-codes branch from ea3c09a to 8eae24c Compare January 25, 2023 12:10
Base automatically changed from 675-support-static-qr-codes to whitelabel January 25, 2023 12:35
@sarahsporck sarahsporck force-pushed the 675-support-static-qr-codes-frontend branch from 4c58936 to fc6bb19 Compare January 26, 2023 09:36
@sarahsporck sarahsporck merged commit 3d544da into whitelabel Jan 26, 2023
@sarahsporck sarahsporck linked an issue Jan 26, 2023 that may be closed by this pull request
@sarahsporck sarahsporck deleted the 675-support-static-qr-codes-frontend branch January 26, 2023 14:07
@maxammann
Copy link
Member

Is there already a task?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support static QR codes
3 participants