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

Consider a token caching facility #80

Open
jessepeterson opened this issue Sep 13, 2024 · 0 comments
Open

Consider a token caching facility #80

jessepeterson opened this issue Sep 13, 2024 · 0 comments

Comments

@jessepeterson
Copy link
Member

jessepeterson commented Sep 13, 2024

Apple has been adding tokens to DEP such as the MAID JWT and Beta OS tokens. Consider adding a token caching facility to NanoDEP. Some ideas/considerations:

  • Light-weight, simple, perhaps just a KV (dict/map/hash) store
  • Flexible cache invalidation depending on token-type
  • Arbitrary enough for unknown future tokens
  • Perhaps just a raw DEP fetch cache/middleware? I.e. potential to work for both depserver proxy and godep.
  • Further consideration on token keying: e.g. is it per-account (DEP name), per-device, other?
  • Invalidation on OAuth and/or token PKI changes
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

No branches or pull requests

1 participant