Skip to content

Conversation

@fkwp
Copy link
Contributor

@fkwp fkwp commented Aug 13, 2025

No description provided.

@fkwp fkwp requested a review from a team as a code owner August 13, 2025 15:51
@fkwp fkwp requested a review from AndrewFerr August 13, 2025 15:51
Copy link

@toger5 toger5 left a comment

Choose a reason for hiding this comment

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

The refactored readme looks good.

This is slightly off topic but is the creation of the tokoen really not sending a request to the sfu itself? To me it seems like the sfu would have to know about the token so I cannot imagine how it would work without a request between authorization service and sfu.

I am talking about the loop arrow here:
Screenshot 2025-08-21 at 12 48 00

@fkwp
Copy link
Contributor Author

fkwp commented Aug 21, 2025

The refactored readme looks good.

This is slightly off topic but is the creation of the tokoen really not sending a request to the sfu itself? To me it seems like the sfu would have to know about the token so I cannot imagine how it would work without a request between authorization service and sfu.

I am talking about the loop arrow here: Screenshot 2025-08-21 at 12 48 00

the token is derived from a shared secret between the lk-jwt-service and the SFU

@fkwp fkwp merged commit ead6df4 into main Aug 21, 2025
4 checks passed
@fkwp fkwp deleted the fkwp/doc/update branch August 21, 2025 11:01
@fkwp fkwp mentioned this pull request Aug 21, 2025
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.

3 participants