[$75] Tasks: Access issue on challenge details page

[SathyaJayabal]

User is able to see a task assigned to them on the challenge listings page, But get the error "You don't have access to view this challenge" when accessing the challenge details page.

example:
user:picachui
https://beta-community-app.topcoder.com/challenges/4db7f854-5c74-41b9-a0f9-b1c03245cfa9

[rootelement]

I believe this is fixed:
https://beta-community-app.topcoder.com/challenges/7db724d4-7cf6-4e99-a045-0472f253e3a5

The UUID got destroyed by the re-migration, but the tasks show up now. The issue was comparing a member ID as a Number to a String. Thomas fixed it in
cd8ba6b#diff-6bf820f045aeaa766c1cac9497c693f5R949

[SathyaJayabal]

@rootelement , I still the issue
https://beta-community-app.topcoder.com/challenges/4096df0c-57eb-4035-a496-e1aaeb2338a9

[rootelement]

@ThomasKranitsas Can you please test this?

In prod, with this cURL:

curl --location --request GET 'https://api.topcoder.com/v5/resources?challengeId=4096df0c-57eb-4035-a496-e1aaeb2338a9&roleId=732339e7-8e30-49d7-9198-cccf9451e221' \
--header 'Authorization: Bearer CHALLENGE_M2M' \
--data-raw ''

I'm seeing the picachui account attached:

[
    {
        "legacyId": 1916645,
        "created": "2020-07-15T04:35:34Z",
        "createdBy": "jaya.dhaka",
        "updated": "2020-07-15T04:36:48Z",
        "updatedBy": "picachui",
        "memberId": "22778049",
        "memberHandle": "picachui",
        "challengeId": "4096df0c-57eb-4035-a496-e1aaeb2338a9",
        "roleId": "732339e7-8e30-49d7-9198-cccf9451e221",
        "id": "f886ce18-1ee7-4fc5-9fef-68adf309e966",
        "rating": 1036
    }
]

[SathyaJayabal]

@rootelement @ThomasKranitsas , so I can see tasks on my listings page, but i get the error only when I click on it and access the details page.

[ThomasKranitsas]

@rootelement fixed in:

• Fix security issues #262
• Fix patch payload challenge-processor#1

It worked fine on dev. Currently deploying on prod.

[ThomasKranitsas]

Another fix: #263

[ThomasKranitsas]

one last fix: #264

[rootelement]

@SathyaJayabal can you please retest this?