mirror of
https://github.com/unshackle-dl/unshackle.git
synced 2026-11-16 22:15:07 +00:00
Deployed f1e40813 with MkDocs version: 1.6.1
This commit is contained in:
@@ -2878,7 +2878,7 @@ that reads <code>error_code</code> to classify a <code>429</code> must cope with
|
||||
</span></code></pre></div>
|
||||
<p>The REST API authenticates with <code>X-Secret-Key</code>. The middleware advertises <code>Authorization</code> because the co-hosted pywidevine / pyplayready CDM endpoints use it. <code>PUT</code> appears in the allowed-methods list, but no REST route uses it. Only <code>GET</code>, <code>POST</code>, and <code>DELETE</code> have routes.</p>
|
||||
<h3 id="where-device-access-is-read">Where device access is read<a class="headerlink" href="#where-device-access-is-read" title="Permanent link">¶</a></h3>
|
||||
<p>The map of accepted API keys lives at <code>request.app["config"]["users"]</code>. For DRM operations, an API key's permitted Widevine devices come from its <code>devices</code> list, and PlayReady devices from <code>playready_devices</code>. The server uses the first configured device when a request does not (or may not) override it. A server-wide <code>config.cdm[<service>]</code> mapping, if present, takes precedence over the API key's device list when the server chooses which device to use.</p>
|
||||
<p>The map of accepted API keys lives at <code>request.app["config"]["users"]</code>. For DRM operations, an API key's permitted Widevine devices come from its <code>devices</code> list, and PlayReady devices from <code>playready_devices</code>. The server uses the first configured device when a request does not (or may not) override it. A <code>cdm</code> entry for the service takes precedence over the API key's device list when the server chooses which device to use: the API key's own <code>serve.users.<key>.cdm</code> entry, else the server-wide <code>config.cdm[<service>]</code> mapping.</p>
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -2847,7 +2847,12 @@ mid-prompt.</p>
|
||||
cannot read each other's cached tokens. The server deletes the directory when the
|
||||
remote session ends. A remote session that uses a server account (<code>serve.server_accounts</code>)
|
||||
gets a persistent per-account cache instead, so the account's tokens outlive the
|
||||
remote session. The server and the client both refuse a forwarded cache file that is not
|
||||
remote session. A service can name cache files that hold its device identity in
|
||||
<code>Service.IDENTITY_CACHE</code>. A remote session on the server's device, or of an API key with its
|
||||
own device config, writes those files to a directory of the API key, outside the remote
|
||||
session's directory, so the server never sends them to the client and never takes them from
|
||||
the client, and the next remote session of that
|
||||
API key reads them again. The server and the client both refuse a forwarded cache file that is not
|
||||
JSON or that names a type other than a date or time, and the service then authenticates again.</li>
|
||||
<li><strong>A tunnel belongs to its API key.</strong> The server accepts <code>tunnel:<id></code> only from the API key
|
||||
that opened the tunnel. Its SOCKS5 proxy listens on loopback only, and it needs a username and
|
||||
@@ -3117,7 +3122,9 @@ returns <code>{ "status": "accepted" }</code>. A post with no pending prompt is
|
||||
On <code>DELETE</code>, when the login belongs to the client (<code>client_auth</code>) and the remote
|
||||
session does not run on the server's device, the handler harvests updated cache files from the whole directory tree (compressing each
|
||||
with zlib and base64-encoding, <strong>excluding</strong> <code>titles_*</code> files) and returns them
|
||||
under a <code>cache</code> field, so the client can keep refreshed tokens. Each cache key
|
||||
under a <code>cache</code> field, so the client can keep refreshed tokens. A remote session on the
|
||||
server's device keeps the files of the service's <code>IDENTITY_CACHE</code> in
|
||||
<code>_identity/<namespace>/<service></code> instead, so they are never in that tree. Each cache key
|
||||
is the file path relative to that directory, with <code>/</code> separators and no <code>.json</code>
|
||||
suffix, which is the <code>Cacher</code> cache key the service reads it with:</p>
|
||||
<div class="language-json highlight"><pre><span></span><code><span id="__span-10-1"><a id="__codelineno-10-1" name="__codelineno-10-1" href="#__codelineno-10-1"></a><span class="p">{</span>
|
||||
|
||||
Reference in New Issue
Block a user