tree f176a0684e7bd1f50c9a4d24a36cf73908d013a5
parent 64412bb9cd9b38e87e2d8a85ebd252a3feae457f
author Hasini Gunasinghe <hasinitg@google.com> 1682955186 +0000
committer Hasini Gunasinghe <hasinitg@google.com> 1683153210 +0000

Challenge is expected in timestamp token in case 2

In the second case out of the two cases of authorization enforcement
described for update(), it seems like the challenge is expected in
the timestamp token.

Test: N/A
Change-Id: I33e1b84bf8218335665b31ca144b3b4ecb342328