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.

Sign up for GitHub

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

Jump to bottom

InvalidClientTaaAcceptanceError time too precise error if container timezone is not UTC #2419

Closed
Ennovate-com opened this issue Aug 14, 2023 · 2 comments
Closed

InvalidClientTaaAcceptanceError time too precise error if container timezone is not UTC #2419

Ennovate-com opened this issue Aug 14, 2023 · 2 comments

Comments

@Ennovate-com
Copy link
Contributor

When running in a container where the timezone is not UTC, acceptance of the TAA results in an error:

 InvalidClientTaaAcceptanceError('Txn Author Agreement acceptance time 1691989200 is too precise and is a privacy risk.',)```

The agreement acceptance time should always reflect a time of midnight in UTC, regardless of the default timezone.
@Ennovate-com
Copy link
Contributor Author

This change should be made wherever the TAA acceptance time is being calculated. There are two places in ACA-Py fixed by PR #2420 places and one place in Indy VDR fixed by PR #211.

andrewwhitehead added a commit that referenced this issue Sep 14, 2023
@andrewwhitehead
Merge pull request #2420 from Ennovate-com/bugfix/time-too-precise
428ec90 
Issue #2419 InvalidClientTaaAcceptanceError time too precise error if container timezone is not UTC
@Ennovate-com
Copy link
Contributor Author

Fixed by PR #2420

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Ennovate-com