librespot/oauth/Cargo.toml

[package]
name = "librespot-oauth"
version = "0.6.0"
rust-version.workspace = true
authors = ["Nick Steel <nick@nsteel.co.uk>"]
description = "OAuth authorization code flow with PKCE for obtaining a Spotify access token"
license = "MIT"
repository = "https://github.com/librespot-org/librespot"
edition = "2021"

[dependencies]
log = "0.4"
oauth2 = "4.4"
thiserror = "1.0"
url = "2.2"

[dev-dependencies]
env_logger =  { version = "0.11.2", default-features = false, features = ["color", "humantime", "auto-color"] }
Credentials with access token (oauth) (#1309) * core: Create credentials from access token via OAuth2 * core: Credentials.username is optional: not required for token auth. * core: store auth data within session. We might need this later if need to re-auth and original creds are no longer valid/available. * bin: New --token arg for using Spotify access token. Specify 0 to manually enter the auth code (headless). * bin: Added --enable-oauth / -j option. Using --password / -p option will error and exit. * core: reconnect session if using token authentication Token authenticated sessions cannot use keymaster. So reconnect using the reusable credentials we just obtained. Can perhaps remove this workaround once keymaster is replaced with login5. * examples: replace password login with token login 2024-09-13 05:35:55 +00:00			`[package]`
			`name = "librespot-oauth"`
Update Cargo.lock 2024-10-30 20:11:33 +00:00			`version = "0.6.0"`
Cargo: use rust-version from workspace (#1375) Make it easier to check and update. 2024-10-17 15:01:56 +00:00			`rust-version.workspace = true`
Credentials with access token (oauth) (#1309) * core: Create credentials from access token via OAuth2 * core: Credentials.username is optional: not required for token auth. * core: store auth data within session. We might need this later if need to re-auth and original creds are no longer valid/available. * bin: New --token arg for using Spotify access token. Specify 0 to manually enter the auth code (headless). * bin: Added --enable-oauth / -j option. Using --password / -p option will error and exit. * core: reconnect session if using token authentication Token authenticated sessions cannot use keymaster. So reconnect using the reusable credentials we just obtained. Can perhaps remove this workaround once keymaster is replaced with login5. * examples: replace password login with token login 2024-09-13 05:35:55 +00:00			`authors = ["Nick Steel <nick@nsteel.co.uk>"]`
			`description = "OAuth authorization code flow with PKCE for obtaining a Spotify access token"`
			`license = "MIT"`
			`repository = "https://github.com/librespot-org/librespot"`
			`edition = "2021"`

			`[dependencies]`
			`log = "0.4"`
			`oauth2 = "4.4"`
			`thiserror = "1.0"`
			`url = "2.2"`

			`[dev-dependencies]`
Discovery: Refactor and add Avahi DBus backend (#1347) * discovery: use opaque error type for DnsSdError This helps to decouple discovery and core by not leaking implementation details of the zeroconf backend into Error conversion impls in core. * discovery: map all MDNS/DNS-SD errors to DiscoveryError::DnsSdError previously, libmdns errors would use a generic conversion from std::io::Error to core::Error * discovery: use an opaque type for the handle to the DNS-SD service * discovery: make features additive i.e. add with-libmdns instead of using not(with-dns-sd). The logic is such that enabling with-dns-sd in addition to the default with-libmdns will still end up using dns-sd, as before. If only with-libmdns is enabled, that will be the default. If none of the features is enabled, attempting to build a `Discovery` will yield an error. * discovery: add --zeroconf-backend CLI flag * discovery: Add minimal Avahi zeroconf backend * bump MSRV to 1.75 required by zbus >= 4 * discovery: ensure that server and dns-sd backend shutdown gracefully Previously, on drop the the shutdown_tx/close_tx, it wasn't guaranteed the corresponding tasks would continue to be polled until they actually completed their shutdown. Since dns_sd::Service is not Send and non-async, and because libmdns is non-async, put them on their own threads. * discovery: use a shared channel for server and zeroconf status messages * discovery: add Avahi reconnection logic This deals gracefully with the case where the Avahi daemon is restarted or not running initially. * discovery: allow running when compiled without zeroconf backend... ...but exit with an error if there's no way to authenticate * better error messages for invalid options with no short flag 2024-10-26 14:45:02 +00:00			`env_logger = { version = "0.11.2", default-features = false, features = ["color", "humantime", "auto-color"] }`