Could we remove this functional token?

[mmyyrroonn]

Is your feature request related to a problem? Please describe.
Looks like this token is still valid and we should remove it.

[haroldrandom]

add it to S163

[mmyyrroonn]

@haroldrandom Please take a look at these two lines

azure-cli/CredScanSuppressions.json

Line 285 in 807facc

"placeholder": "0abf356884d74b4aacbd7b1ebd3da0f7",

and

azure-cli/CredScanSuppressions.json

Line 293 in 807facc

"placeholder": "5+36OCtbIwfy8g5glC4bQQrFsfmMc3iD",

[haroldrandom]

I think it should own by service team. The accessToken is used in test_ams_live_event_scenarios.py is hard coded. Should be get online through command.

Added "Service Attension" for further help.

[yonzhan]

@fredericky @akucer @yulei, could you please help with above hard coded accessToken issue from Media Services team?

[haroldrandom]

Add an example #12589 (comment)

[hivyas]

The accessToken is used in test_ams_live_event_scenarios.py is actually named poorly because it is a GUID and not an actual security token. I have updated the code to use a generated GUID instead of a hardcoded one in order to avoid confusion: #13948.

The second hardcoded string is found in the container module and AMS does not own that.

[haroldrandom]

Add one related issue Azure/azure-cli-dev-tools#215

[akucer]

@haroldrandom - I removed the Media Services label and assignment to AMS team members as AMS issue has been fixed. As per previous comment the other hardcoded string is not owned by AMS and needs assignment to appropriate team / owner. Thanks.