Skip to content

Require login and Wipro All membership for Topgear - #2427

Merged
jmgasper merged 1 commit into
devfrom
fix/topgear-wipro-access
Oct 2, 2026
Merged

jmgasper merged 1 commit into
devfrom
fix/topgear-wipro-access

Conversation

@jmgasper

@jmgasper jmgasper commented Oct 1, 2026 •

Copy link
Copy Markdown
Collaborator

Topgear previously rendered its Opportunities listing for anonymous visitors. All routes on the Topgear host now require a logged-in profile and an authenticated Groups API response confirming membership in Wipro - All before the route tree mounts.

Anonymous users are sent to login with their full return URL, including query parameters and fragments. Non-members see an access-restricted page; pending checks and errors never render or fetch challenge content. Checks are canceled when obsolete and repeated when the member or path changes. This also covers direct challenge details and other routes on the Topgear hostname. Other hosts retain their normal access behavior.

The access group defaults to b7f7c0f8-8ee8-409e-9e5c-33404983b635 (verified as Wipro - All), with REACT_APP_TOPGEAR_ACCESS_GROUP_ID separate from the challenge listing filter. Membership comes from /v6/groups/memberGroups/:memberId?uuid=true, including active parent memberships; email suffixes and cookie presence do not grant access. Existing Challenge API authorization remains in place.

Validation: 35 focused tests cover anonymous login, pending checks, members/non-members, failures and retry, obsolete requests, profile changes, malformed API responses, direct routes, and existing Opportunities routing. Companion avatar-menu links: topcoder-platform/universal-navigation#417.

Full yarn lint and LOGICAL_ENV=dev yarn run build pass. The dev build is published and its served HTML matches the local build; the CloudFront invalidation completed. Live anonymous and invalid-session browser checks reach login with the complete return URL and issue zero challenge requests. Browser checks against the deployed app with controlled profile/membership responses confirm member access, non-member denial, API-error denial, direct-detail denial, and normal behavior on the non-Topgear host. A valid dev member session was unavailable (the supplied production token is rejected by dev); positive membership was checked using fixtures, and the production Groups API independently confirmed the Wipro group ID and token owner’s membership. The existing /challenges HTTP 302 still preserves repeated query parameters.

@jmgasper
jmgasper requested a review from kkartunov as a code owner October 1, 2026 23:48
@jmgasper
jmgasper merged commit 10d5a59 into dev Oct 2, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant