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

DPS: implement AccessTokenDataStore #3893

Closed
Tracked by #3892
paullatzelsperger opened this issue Feb 21, 2024 · 0 comments · Fixed by #3907
Closed
Tracked by #3892

DPS: implement AccessTokenDataStore #3893

paullatzelsperger opened this issue Feb 21, 2024 · 0 comments · Fixed by #3907
Labels
dpf Feature related to the Data Plane Framework enhancement New feature or request
Milestone

Comments

@paullatzelsperger
Copy link
Member

paullatzelsperger commented Feb 21, 2024

Feature Request

In order to keep track of valid tokens, the data plane needs to have a record of AccessTokenData objects.
Those are POJOs that contain information about the claims and the DataAddress associated with a transfer:

public record AccessTokenData(ClaimToken claimToken, DataAddress address, String id)

For testing/demo purposes we should have an in-memory implementation, but for production scenarios we need a persistent
store based on Postgres.

Which Areas Would Be Affected?

data plane

Why Is the Feature Desired?

data plane instances need to be able to validate the access token on an incoming data request.

@paullatzelsperger paullatzelsperger added dpf Feature related to the Data Plane Framework enhancement New feature or request labels Feb 21, 2024
@paullatzelsperger paullatzelsperger added this to the Milestone 14 milestone Feb 21, 2024
@paullatzelsperger paullatzelsperger changed the title Dataplane Signaling: implement AccessTokenDataStore DPS: implement AccessTokenDataStore Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dpf Feature related to the Data Plane Framework enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant