You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As asked in #51 (comment), evaluate what it takes to add support for direct connection between CLI and device (without involvement of my JD). This will probably need update in client library
The text was updated successfully, but these errors were encountered:
For what it's worth, JD has a deprecated API available in the Advanced Settings flags. Under normal circumstances I think you connect via MyJD and then after authenticating the session it attempts to connect directly to local instances of JD and falls back to the MyJD relay if this fails, though how it does this is a black box and isn't really documented.
The deprecated API needs to be manually enabled via a flag (followed by a JD restart) and listens on port 3128. By default it only listens on localhost but another flag will allow LAN connections. It allows unauthenticated API calls to be made (same endpoints as the modern MyJD API), I think this is how that Python library attempts to connect to JD directly.
As asked in #51 (comment), evaluate what it takes to add support for direct connection between CLI and device (without involvement of my JD). This will probably need update in client library
The text was updated successfully, but these errors were encountered: