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

Capability attestation #213

Open
jot2re opened this issue Dec 1, 2021 · 2 comments · May be fixed by #214
Open

Capability attestation #213

jot2re opened this issue Dec 1, 2021 · 2 comments · May be fixed by #214
Assignees

Comments

@jot2re
Copy link
Collaborator

jot2re commented Dec 1, 2021

Per request from @colourful-land we need to construct a new object called Capability Attestation, which can be used by Token Negotiator to preemptively fetch a token for a specific site.
We agreed that such an attestation would include the following fields:

  1. Unique ID (big Integer)
  2. Domain (URL)
  3. notBefore (Unix time)
  4. notAfter (Unix time
  5. Capabilities (Integer or bit string. In the integer case each bit of the integer will represent a capability granted if the bit is 1)
@jot2re jot2re self-assigned this Dec 1, 2021
@jot2re
Copy link
Collaborator Author

jot2re commented Dec 2, 2021

@colourful-land can you give me a list of the initial capabilities you are thinking about? So far I am just adding, read, write and deletage.

@jot2re jot2re linked a pull request Dec 2, 2021 that will close this issue
@jot2re jot2re linked a pull request Dec 2, 2021 that will close this issue
@AW-STJ AW-STJ moved this to In Progress: TokenScript in TokenScript Dec 14, 2021
@AW-STJ
Copy link
Contributor

AW-STJ commented Feb 16, 2022

@weiwu-zhang - can you please provide some feedback to Tore on this issue?

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

Successfully merging a pull request may close this issue.

2 participants