Anyone using password protection for RTCMulticonnection?

[rayj00]

I am running RTCMulticonnection v.3.7.0

Has anyone got the password protection to work?

Thanks,

Ray

[wnsvy223]

I am using version 3.6.9 on my website. Password function in 3.6.9 is operating normally. If you look at the git commit history, the password part of 3.6.9 and 3.7.0 has no difference in function. Therefore, version 3.7.0 will work as well.

[rayj00]

Thanks. Do you code for the password function?

From: wnsvy223 [mailto:[email protected]] Sent: Friday, June 12, 2020 2:20 AM To: muaz-khan/WebRTC-Experiment [email protected] Cc: rayj00 [email protected]; Author [email protected] Subject: Re: [muaz-khan/WebRTC-Experiment] Anyone using password protection for RTCMulticonnection? (#678)

I am using version 3.6.9 on my website. Password function in 3.6.9 is operating normally. If you look at the git commit history, the password part of 3.6.9 and 3.7.0 has no difference in function. Therefore, version 3.7.0 will work as well.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/muaz-khan/WebRTC-Experiment/issues/678#issuecomment-643088268 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSNU4Z4C6FTLQEFKRCESUTRWHCHZANCNFSM4NZWGJEQ .

[wnsvy223]

https://www.rtcmulticonnection.org/docs/password/ It's simple. Just follow the link above. If you don't know anything, refer to the document and it will be mostly solved.

[rayj00]

Will this work for Scalable Broadcasting also?

From: wnsvy223 [mailto:[email protected]] Sent: Friday, June 12, 2020 8:40 AM To: muaz-khan/WebRTC-Experiment [email protected] Cc: rayj00 [email protected]; Author [email protected] Subject: Re: [muaz-khan/WebRTC-Experiment] Anyone using password protection for RTCMulticonnection? (#678)

https://www.rtcmulticonnection.org/docs/password/ It's simple. Just follow the link above. If you don't know anything, refer to the document and it will be mostly solved.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/muaz-khan/WebRTC-Experiment/issues/678#issuecomment-643248988 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSNU4ZIY27FJF765BL4WWTRWIOZVANCNFSM4NZWGJEQ .

[rayj00]

I was looking at this. Where does the connection.password = ‘abcdef’ go? Surely not in the index.html?

From: wnsvy223 [mailto:[email protected]] Sent: Friday, June 12, 2020 8:40 AM To: muaz-khan/WebRTC-Experiment [email protected] Cc: rayj00 [email protected]; Author [email protected] Subject: Re: [muaz-khan/WebRTC-Experiment] Anyone using password protection for RTCMulticonnection? (#678)

https://www.rtcmulticonnection.org/docs/password/ It's simple. Just follow the link above. If you don't know anything, refer to the document and it will be mostly solved.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/muaz-khan/WebRTC-Experiment/issues/678#issuecomment-643248988 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSNU4ZIY27FJF765BL4WWTRWIOZVANCNFSM4NZWGJEQ .

[rayj00]

I don’t think this works with Scaleable Broadcast.

From: wnsvy223 [mailto:[email protected]] Sent: Friday, June 12, 2020 8:40 AM To: muaz-khan/WebRTC-Experiment [email protected] Cc: rayj00 [email protected]; Author [email protected] Subject: Re: [muaz-khan/WebRTC-Experiment] Anyone using password protection for RTCMulticonnection? (#678)

https://www.rtcmulticonnection.org/docs/password/ It's simple. Just follow the link above. If you don't know anything, refer to the document and it will be mostly solved.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/muaz-khan/WebRTC-Experiment/issues/678#issuecomment-643248988 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSNU4ZIY27FJF765BL4WWTRWIOZVANCNFSM4NZWGJEQ .

[wnsvy223]

I tested it. As you said, the password function does not work in the Scaleable Broadcast example. I couldn't find a solution because my coding skills were not so good. If there is no solution to the API, I think you should control it directly from your signaling server.