Skip to content

Conversation

enesuludg
Copy link

  • Add CanPublish field to TesterParams and Params structs
  • Add --disable-publish flag to both perf load-test and load-test commands
  • Implement custom token generation with canPublish permission control
  • Update LoadTester.Start() to use custom tokens when canPublish is false
  • Maintain backward compatibility with existing behavior
  • Rename conflicting newAccessToken in agentloadtester.go to newAgentAccessToken

This allows users to test scenarios where participants cannot publish tracks by setting canPublish: false in JWT tokens.

- Add CanPublish field to TesterParams and Params structs
- Add --disable-publish flag to both perf load-test and load-test commands
- Implement custom token generation with canPublish permission control
- Update LoadTester.Start() to use custom tokens when canPublish is false
- Maintain backward compatibility with existing behavior
- Rename conflicting newAccessToken in agentloadtester.go to newAgentAccessToken

This allows users to test scenarios where participants cannot publish tracks
by setting canPublish: false in JWT tokens.
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@davidzhao
Copy link
Member

by default it doesn't publish anything, and a user could already adjust with video-publishers and audio-publishers flags. why is it needed to remove publish permissions?

@enesuludg
Copy link
Author

by default it doesn't publish anything, and a user could already adjust with video-publishers and audio-publishers flags. why is it needed to remove publish permissions?

In our application’s case, user permissions directly affect the flow, so I added it for that reason. I thought it might also be useful for others who have similar needs.

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.

4 participants