Skip to content

fix: remove SuperAdminAuthGuard from GET /partner/:name (closes #1042)#1049

Open
KJyang-0114 wants to merge 1 commit intochaynHQ:developfrom
KJyang-0114:fix/issue-1042-remove-superadmin-auth
Open

fix: remove SuperAdminAuthGuard from GET /partner/:name (closes #1042)#1049
KJyang-0114 wants to merge 1 commit intochaynHQ:developfrom
KJyang-0114:fix/issue-1042-remove-superadmin-auth

Conversation

@KJyang-0114
Copy link
Copy Markdown

Summary

Removes the SuperAdminAuthGuard from the GET /v1/partner/:name endpoint to make it publicly accessible. This is needed because partner config data (logos, websites, social links) is being moved to the database and the frontend needs to call this endpoint to display partner branding.

Changes

  • Removed @UseGuards(SuperAdminAuthGuard) decorator from GET :name endpoint
  • Updated @ApiOperation description to indicate this is a public endpoint
  • Other endpoints (POST, GET all, PATCH) remain admin-only

Testing

  • The change is minimal and follows the existing comment in the codebase: // Temporary super admin auth guard
  • Manual testing: call GET /v1/partner/[test-partner] without an auth token

Closes #1042

- Removed @UseGuards(SuperAdminAuthGuard) decorator from GET :name endpoint
- Updated ApiOperation description to indicate this is a public endpoint
- Partner config data (logos, websites, social links) is non-sensitive
- Other endpoints (POST, GET all, PATCH) remain admin-only

Closes chaynHQ#1042
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.

Remove SuperAdminAuthGuard from GET /partner/:name

1 participant