You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2021/01/15 21:24:01 UTC

[GitHub] [trafficcontrol] ocket8888 commented on issue #5443: PUT users/{id} endpoint has incorrect use of COALESCE for field new_user

ocket8888 commented on issue #5443:
URL: https://github.com/apache/trafficcontrol/issues/5443#issuecomment-761204538


   I think the purpose of the `new_user` field is to cause TP to prompt them to change/set their password on login. The intention is that if that hasn't yet occurred, then the user is still "new". If someone else updates the user object e.g. because they realized the user needs to be in a higher tenant before the user completes registration, then it won't properly prompt then on their first login if you make this change. I think the behavior is currently working as intended, roughly. The only thing is that _any_ update through `user/current` is unsetting that field, when really I think it should only count password updates. But that's just my opinion.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org