Open gavination opened 6 years ago
Passing in a token generated from the chaos-token command yields an improper token for Live IDs
chaos-token
chaos token
Bearer
\u001b[49m\u001b[39m
accessToken
chaos start
chaos stop
Targeted Azure resource should be enabled/disabled.
Error returned: The access token is from the wrong issuer 'https://sts.windows.net/f8cdef31-a31e-4b4a-93e4-5f571e91255a/'. It must match the tenant 'https://sts.windows.net/44c19e06-2387-4136-85e6-a8a486c5e037/'
Thinking a service principal may be able to circumvent this issue. Going to give that a try this week. Keeping this comment for bookkeeping purposes.
Description
Passing in a token generated from the
chaos-token
command yields an improper token for Live IDsSteps to Reproduce
chaos token
command and undergo Interactive LoginBearer
and stop right before\u001b[49m\u001b[39m
accessToken
flag in eitherchaos start
orchaos stop
commandsExpected Behavior
Targeted Azure resource should be enabled/disabled.
Actual Behavior
Error returned: The access token is from the wrong issuer 'https://sts.windows.net/f8cdef31-a31e-4b4a-93e4-5f571e91255a/'. It must match the tenant 'https://sts.windows.net/44c19e06-2387-4136-85e6-a8a486c5e037/'