Skip to content
This repository has been archived by the owner on Jul 31, 2024. It is now read-only.

Consider more metadata for clients and resources #2285

Closed
leastprivilege opened this issue May 2, 2018 · 5 comments
Closed

Consider more metadata for clients and resources #2285

leastprivilege opened this issue May 2, 2018 · 5 comments
Milestone

Comments

@leastprivilege
Copy link
Member

resources: created, updated
clients: created, updated, last access

@leastprivilege
Copy link
Member Author

This has of course implications - because to maintain those values (e.g. client last access) we would need write access to the config store.

@brockallen
Copy link
Member

which of these do we want tin 2.3?

@leastprivilege
Copy link
Member Author

all of them - some are useful for admin interfaces.

client last access is something I heard a couple of times - we don't have to use it internally - but that timestamp could easily be set in an ext. point.

@leastprivilege leastprivilege modified the milestones: Future, 2.3 Aug 3, 2018
@brockallen
Copy link
Member

ok, done. also added LastAccessed to APiResource if the desire is to track last client/api authentication (think introspection).

do we also want a LastAccessed on the secret table?

@lock
Copy link

lock bot commented Jan 13, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants