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

Add CCA Token example #176

Open
wants to merge 9 commits into
base: main
Choose a base branch
from
Open

Add CCA Token example #176

wants to merge 9 commits into from

Conversation

gmandyam
Copy link

@gmandyam gmandyam commented Jan 3, 2025

To address #172

@hannestschofenig
Copy link
Collaborator

Thanks for the contribution, Giri. The text is good but I am wondering why you only included the Platform Evidence token instead of also the Realm token. Could you explain?

gmandyam and others added 4 commits January 3, 2025 10:45
@gmandyam
Copy link
Author

gmandyam commented Jan 3, 2025

Thanks for the contribution, Giri. The text is good but I am wondering why you only included the Platform Evidence token instead of also the Realm token. Could you explain?

I had not created a sample realm claim set yet, and this issue was pending for a while so I wanted to get something in for review. I can add a realm token example.

One more question: will a single OID be allocated for CCA token? Or can different OID's be assigned for the different CCA attestation options? I think t least for CSR's there could potentially be three: (a) Platform token only, (b) DIrect model: Platform token + realm claims set, where a hash of the realm claims set is included in the platform token payload as challenge data, and (c) Delegated model: Platform token + Realm Attestation Token, where Platform token includes the Realm Attestation PubKey as challenge data. Another option is to just assign one OID for CCA, and have the variants be identified by CBOR tags.

gmandyam and others added 2 commits January 8, 2025 08:43
Co-authored-by: Hannes Tschofenig <[email protected]>
@hannestschofenig
Copy link
Collaborator

In your case I think it would be best to assign three OIDs - one for each of the encodings.

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.

2 participants