Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for direct connection to device #53

Open
rkosegi opened this issue Nov 14, 2024 · 1 comment
Open

Add support for direct connection to device #53

rkosegi opened this issue Nov 14, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@rkosegi
Copy link
Owner

rkosegi commented Nov 14, 2024

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

@rkosegi rkosegi added the enhancement New feature or request label Nov 14, 2024
@HeyItsJono
Copy link

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.

image

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants