You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In certain cases, shared user accounts may get to have a big number of assigned tokens. I've seen cases with more than 50 tokens per account.
By leveraging the existing functionality, to be able to find tokens that haven't been used for more than XXX, we could also add owner information to the query.
There is already the tokeninfo query, adding a tokenowner query would greatly improve this functionality.
Thank you for filing an issue and sharing your observations or ideas. Please be sure to provide as much information as possible to help us to work on this issue.
We would also need the resolver, to find the corresponding valu ein the tokenowner table.
However, when specifiying the user_id this is fine, since we would not need a resolver-request to e.g. LDAP.
In certain cases, shared user accounts may get to have a big number of assigned tokens. I've seen cases with more than 50 tokens per account.
By leveraging the existing functionality, to be able to find tokens that haven't been used for more than XXX, we could also add owner information to the query.
There is already the tokeninfo query, adding a tokenowner query would greatly improve this functionality.
For example
The text was updated successfully, but these errors were encountered: