Skip to content

DIsable auth #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 30, 2025
Merged

DIsable auth #1

merged 1 commit into from
Jun 30, 2025

Conversation

kkartunov
Copy link
Contributor

No description provided.

@@ -20,27 +20,27 @@ import { APP_GUARD } from '@nestjs/core';
sessionIdGenerator: () => randomUUID(),
statelessMode: false,
},
guards: [AuthGuard, RolesGuard],
// guards: [AuthGuard, RolesGuard],

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high
security
Commenting out the guards AuthGuard and RolesGuard disables authentication and role-based access control. Ensure this is intentional and consider the security implications of deploying this change to production.

useClass: RolesGuard,
},
// {
// provide: APP_GUARD,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high
security
Commenting out the APP_GUARD providers for AuthGuard and RolesGuard will disable these guards globally. Verify that this change is intended and assess the impact on application security.

QueryChallengesTool,
],
})
export class AppModule implements NestModule {
configure(consumer: MiddlewareConsumer) {
consumer.apply(TokenValidatorMiddleware).forRoutes('*');
consumer.apply(CreateRequestStoreMiddleware).forRoutes('*');
// consumer.apply(TokenValidatorMiddleware).forRoutes('*');

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high
security
Commenting out TokenValidatorMiddleware and CreateRequestStoreMiddleware will disable these middlewares. Ensure this is intentional and consider the potential impact on request validation and request context management.

.string()
.describe('Winner handle on Topcoder platform'),
userId: z.string().describe('Unique identifier for the user'),
placement: z.number().describe('Placement of the winner'),

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium
correctness
Consider using z.number().int() for placement to ensure that only integer values are accepted, as placements are typically whole numbers.

@kkartunov kkartunov merged commit 1d3ec10 into dev Jun 30, 2025
1 of 2 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