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

PoPCHA: Inconsistencies in the JWT format #1741

Open
K1li4nL opened this issue Feb 10, 2024 · 0 comments
Open

PoPCHA: Inconsistencies in the JWT format #1741

K1li4nL opened this issue Feb 10, 2024 · 0 comments
Labels
be1-go be2-scala popcha proto-spec Everything related to the PoP protocol

Comments

@K1li4nL
Copy link
Contributor

K1li4nL commented Feb 10, 2024

The final JWT token should have a well defined format, but its documentation and implementations are inconsistent, the laoID field is either not present (Go backend) or present but with a field name not mentionned in the relevant documentation:

Be1-Go: from this commit and file
image

Be2-Scala: from this commit and file
image

The doc:
image
@K1li4nL K1li4nL added proto-spec Everything related to the PoP protocol be2-scala be1-go popcha labels Feb 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
be1-go be2-scala popcha proto-spec Everything related to the PoP protocol
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@K1li4nL