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

The attestation controller should correctly populate VC fields #1767

Closed
jleach opened this issue Feb 5, 2024 · 0 comments · Fixed by #1833
Closed

The attestation controller should correctly populate VC fields #1767

jleach opened this issue Feb 5, 2024 · 0 comments · Fixed by #1833
Assignees

Comments

@jleach
Copy link
Member

jleach commented Feb 5, 2024

The schema has been decided on for the attestation credential (#1714) and now the controller should correctly populate these values.

{
  "attributes": [
    "issue_date_dateint",
    "validation_method",
    "app_version",
    "app_vendor",
    "app_id",
    "operating_system",
    "operating_system_version"
  ],
  "schema_name": "app_attestation",
  "schema_version": "1.0"
}

Values to Use

  • "issue_date_dateint". Set to the time the credential was issued.
  • "validation_method". Enum that denotes if App Store Receipts (< iOS 14), Apple Attestation (>= iOS 14), or Google Integrity API was used.
  • "app_version". The mobile version number of the application ie. v1.0.15-1543
  • "app_vendor". The mobile application vender ie. "Government of British Columbia". This will not change for us and can be imported from constatns.
  • "app_id". Use the bundle ID. ie. "ca.bc.gov.BCWallet"
  • "operating_system". Enum that is either "ios" or "android" all lower case. This can be sent by mobile application but I think it is just as accurate and more simple to determine this based on the attestation technique (google vs apple).
  • "operating_system_version". The current version of the mobile operating system. ie. 14.0.3
@jleach jleach mentioned this issue Feb 1, 2024
17 tasks
@jleach jleach self-assigned this Feb 7, 2024
@cvarjao cvarjao closed this as completed Sep 24, 2024
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 a pull request may close this issue.

2 participants