FAQ

Q: How does this work?
A: There is a very in-depth explanation here. But I like to call it *magic*
Q: Is this secure?
A: Kinda. RTT will translate requests to PMS such that they are received as if they were another user. All of the response scenarios haven't been tested/analyzed but it is possible that a user accessing a share in this method could watch the http transactions with a program such as fiddler and gain the access token of the super user. Also, this will enable the user to see plex as if they were the other user. However, RTT is smart enough to deny access to settings and actions such as adding sections, scanning, removing sections, channel management, etc. Other than that, it is no more/less secure than PMS itself.
Q: Does RTT reduce load on PMS?
A: No. RTT will simply delegates requests to the PMS server you designated. Because of this, the load on that particular server will be the same. In its current build, streaming is not currently a good idea as you will always transcode and it will utilize some load balancer resources in the process.
Q: Why do we ghost machines to a user?
A: This is done for 2 reasons:

• Plex needs to know that a server exists at that ip in order to reach out to it automatically when a user logs in.
• Plex is smart enough to verify the machine Id of a discovered server belongs to that of the logged in user on the client side (might be a checksum?). Because of this, we need a uinque mahine id that belongs to the logged in user.