New issue
Advanced search Search tips

Issue 685324 link

Starred by 3 users
Status: Untriaged
Owner: ----
Cc:
zentaro@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
V2



Sign in to add a comment

ChromAD: investigate whether it makes sense to keep user TGTs and machine TGTs in separate processes

Project Member Reported by jorgelo@chromium.org, Jan 25 2017 
Leftover work from security review.

Comment 1 by ljusten@chromium.org, Jan 26 2017

Components: Enterprise
Labels: V2 Chromad M-58 OS-Chrome

Comment 2 by ljusten@chromium.org, Apr 20 2017 

Note that the user's UPN and/or sAMAccountName can change any time on the server. Hence, if the user's TGT is invalid, we have to query the user's sAMAccountName by objectGUID using the device TGT. Then the sAMAccountName can be used to query a new user TGT. Thus, if device and user TGTs are kept in separate processes, this would require some ping-ponging between processes to query a new user TGT.

Comment 3 by ljusten@chromium.org, May 19 2017

Labels: -M-58 Enterprise-Triaged
Owner: ----
Status: Available (was: Assigned)
Returning to the pool.
Project Member

Comment 4 by sheriffbot@chromium.org, May 21 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment