Auth options for qobuz-connect and support in the qonductor library

[nickblt]

Nice work on the player!

I was taking a look at https://github.com/SofusA/qobuz-player/issues/285 and thinking about how qonductor could better suit your use case.

The way qonductor works right now is auth-less.

Auth-less steps:

1. mDNS advertises device → Qobuz app discovers it
2. Qobuz app calls the qonductor webserver and GET /get-connect-info → gets the app_id
3. User selects device in Qobuz app
4. Qobuz app POSTs to /connect-to-qconnect with session_id, jwt_qconnect, and jwt_api
5. Those JWTs are what spawn_session() uses to connect to wss://play.qobuz.com/ws

If your player already has the JWTs (I haven't fully delved into the codebase to know if that's true) qonductor could skip steps 1-4 and have a simpler interface.

For my use case I want to run it auth-less so I never even thought of building it to skip those steps till now.

Would that be a helpful addition to qonductor for you?

[SofusA]

Hey. Thanks!

Yeah we get the jwt token and user id in the login flow in qobuz-player-client/src/client.rs.

I think that would help, but (except for #285), this seems to work

[nickblt]

I added the new auth mechanism to qonductor here nickblt/qonductor@12f64ad and pushed the crate as v0.1.0-alpha.5

You may end up needing to POST to https://www.qobuz.com/api.json/0.2/qws/createToken with body jwt=jwt_qws It seems like qobuz uses different JWTs for the websocket connection

the response payload from that endpoint looks like this:

{
    "jwt_qws": {
        "exp": 1774976562,
        "jwt": "**REDACTED**",
        "endpoint": "wss://qws-us-prod.qobuz.com/ws"
    }
}

Used like this:

let config = DeviceConfig::new(device_name).auto_activate(false);

let mut session = match qonductor::connect(&ws_endpoint, &ws_jwt, &config).await {
    Ok(s) => s,
    Err(e) => {
        eprintln!("Failed to connect: {e}");
    }
};

@hermzz tagging as you might be interested in this change.