backend: Rename recording permission middleware for clarity and consistency
This commit is contained in:
parent
9059780382
commit
0006097d8e
@ -48,7 +48,7 @@ export const withRecordingEnabled = async (req: Request, res: Response, next: Ne
|
||||
}
|
||||
};
|
||||
|
||||
export const withCorrectPermissions = async (req: Request, res: Response, next: NextFunction) => {
|
||||
export const withCanRecordPermission = async (req: Request, res: Response, next: NextFunction) => {
|
||||
const roomId = extractRoomIdFromRequest(req);
|
||||
const payload = req.session?.tokenClaims;
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ import {
|
||||
participantTokenValidator,
|
||||
tokenAndRoleValidator,
|
||||
withRecordingEnabled,
|
||||
withCorrectPermissions,
|
||||
withCanRecordPermission,
|
||||
withValidRecordingFiltersRequest,
|
||||
withValidRecordingBulkDeleteRequest,
|
||||
withValidRecordingId,
|
||||
@ -62,7 +62,7 @@ internalRecordingRouter.post(
|
||||
withValidStartRecordingRequest,
|
||||
withRecordingEnabled,
|
||||
withAuth(participantTokenValidator),
|
||||
withCorrectPermissions,
|
||||
withCanRecordPermission,
|
||||
recordingCtrl.startRecording
|
||||
);
|
||||
|
||||
@ -71,6 +71,6 @@ internalRecordingRouter.post(
|
||||
withValidRecordingId,
|
||||
withRecordingEnabled,
|
||||
withAuth(participantTokenValidator),
|
||||
withCorrectPermissions,
|
||||
withCanRecordPermission,
|
||||
recordingCtrl.stopRecording
|
||||
);
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user