[$50] Plugin not colouring admin handles in orange

[jmgasper]

To get the role for a user:

curl --location --request GET 'http://api.topcoder-dev.com/v3/roles?filter=subjectID%3D23194912' --header 'Authorization: Bearer <token value>'

where 23194912 is the ID for nick.castillo.

The response should contain the roles for a user and we want to show orange for:

• Admin
• admin
• administrator
• Administrator

[jmgasper]

Contest https://www.topcoder.com/challenges/30140229 has been created for this ticket.

This is an automated message for ghostar via Topcoder X

[jmgasper]

Contest https://www.topcoder.com/challenges/30140229 has been updated - it has been assigned to obog.

This is an automated message for ghostar via Topcoder X

[atelomycterus]

@jmgasper Implemented but need to test with m2m Topcoder params. I've tried to use m2m Topcoder values from challenge forum processor but I get the "The machine user should have the scope as 'read:roles'" error:
{ "id":"2e2754a9:17434e56c51:78ff", "result": {"success":true,"status":403,"metadata":null,"content":"The machine user should have the scope as 'read:roles'" }

Member API (/user/stats) used in Topcoder plugin doesn't require any auth headers.

Please provide m2m params, I'll test it.

PRs

topcoder-platform/forums-plugins#17 - Forums issues 24, issue 25
#26 - for issues-24: Added M2M params and topcoder them

New M2M TOKEN params

Need to set env vars to generate M2M token in vanilla.env.
TOPCODER_AUTH0_AUDIENCE=
TOPCODER_AUTH0_CLIENT_ID=
TOPCODER_AUTH0_CLIENT_SECRET=
TOPCODER_AUTH0_PROXY_SERVER_URL=
TOPCODER_AUTH0_URL=

Testing with hard-coded token:

Topcoder Plugin settings

Added the roles API param:

[jmgasper]

@atelomycterus - Thanks. I've requested an M2M key / secret specific to the forums.

[jmgasper]

@atelomycterus - Here are some details and feedback from Topcoder:

1. Can we remove the TOPCODER_ prefix? Just have things like:

"AUTH0_AUDIENCE": "https://m2m.topcoder-dev.com/",
"AUTH0_URL": "https://topcoder-dev.auth0.com/oauth/token",
"AUTH0_PROXY_SERVER_URL": "https://auth0proxy.topcoder-dev.com/token",

Those above are already injected in the CI/CD build

2. I'll email the key/secret we can use for testing

[atelomycterus]

@jmgasper 1. Yes, sure. I'll fix it.

2. Got the same error 'The machine user should have the scope as 'read:roles'':
   

Get a new token:

curl --header "Content-Type: application/json" \
  --request POST \
  --data '{ "grant_type": "client_credentials","client_id": "<CLIENT_ID>","client_secret": "<CLIENT_SECRET>","audience": "https://m2m.topcoder-dev.com/", "auth0_url": "https://topcoder-dev.auth0.com/oauth/token"}' \
  https://auth0proxy.topcoder-dev.com/token

Get roles:

curl --location --request GET 'https://api.topcoder-dev.com/v3/roles?filter=subjectID%3D8547899' --header 'Authorization: Bearer <TOKEN>'

[jmgasper]

@atelomycterus - Should be fixed now, sorry about that.

[atelomycterus]

@jmgasper Still not working.

{"id":"2e2754a9:1744fe78e74:-36c9","result":{"success":true,"status":403,"metadata":null,"content":"The machine user should have the scope as 'read:roles'"},"version":"v3"}

[jmgasper]

@atelomycterus - Sorry about that, checking with Topcoder

[atelomycterus]

@jmgasper I see it's working now. Please apply PR - topcoder-platform/forums-plugins#18 with updated m2m token names. Thanks!

M2M token params

AUTH0_AUDIENCE=
AUTH0_CLIENT_ID=
AUTH0_CLIENT_SECRET=
AUTH0_PROXY_SERVER_URL=
AUTH0_URL=

Colors

The orange color is brighter for admins:

[jmgasper]

Payment task has been updated: https://software.topcoder.com/review/actions/ViewProjectDetails?pid=30140229

This is an automated message for ghostar via Topcoder X