e2corporation commented on issue #2367: URL: https://github.com/apache/incubator-devlake/issues/2367#issuecomment-1168969852
> > @klesh @Startrekzky What is the business value in revealing a username associated with a secure token and displaying it on the UI in the first place? Is backend going to discern username information from the token and provide that information in the connection object for each token? Is username going to be present in the API test response only? GitHub automatically emails users regarding expired tokens or tokens that are about to expire. > > No, it has nothing to do with the BE. > > Yes, the `username` is going to be present in API test response only. > > Email notification for github token, maybe, I'm not sure. But it has nothing to do with the design AFAIK, from what I learned from @yumengwang03, it is for the user who has multiple tokens from different colleagues, so the user could identify which ones are expired, and reach out to the owner easily, plus, the user can find out if there are duplicate `username` from these seemingly different tokens, and we can also check that for them as well. If API is providing this information with the API response, we can get this information displayed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
