Token already had an SHA1 available, performing another SHA1 generation on this creates the wrong value and a later mismatch
1 file changed