Skip to content

fix(prosody): Fixes auth type internal with prosody 13. #2057

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
Mar 22, 2025

Conversation

damencho
Copy link
Member

When that mechanism is enabled we end up in endless loop:

prosody-1  | 2025-03-22T21:01:26.925692034Z 2025-03-22 21:01:26 meet.jitsi:tokenauth                                         warn	Failed to verify access token: (nil)
prosody-1  | 2025-03-22T21:01:27.043438860Z 2025-03-22 21:01:27 meet.jitsi:tokenauth                                         warn	Failed to verify access token: (nil)
.....

Copy link
Member

@saghul saghul left a comment

Choose a reason for hiding this comment

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

How on earth did you figure this one out?!

@damencho
Copy link
Member Author

Well, I managed to repro on non docker, but I saw the endless cycle in prosody logs ... prosody code a little and here we are.

@damencho damencho merged commit 6668c1b into master Mar 22, 2025
2 checks passed
@damencho damencho deleted the fix-internal branch March 22, 2025 23:11
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.

2 participants