+1
Cargo.lock
+1
Cargo.lock
+1
who-am-i/Cargo.toml
+1
who-am-i/Cargo.toml
-34
who-am-i/src/dns_resolver.rs
-34
who-am-i/src/dns_resolver.rs
···-// originally from weaver: https://github.com/rsform/weaver/blob/ee08213a85e09889b9bd66beceecee92ac025801/crates/weaver-common/src/resolver.rs-// MPL 2.0: https://github.com/rsform/weaver/blob/ee08213a85e09889b9bd66beceecee92ac025801/LICENSE
···
+17
-2
who-am-i/src/expiring_task_map.rs
+17
-2
who-am-i/src/expiring_task_map.rs
······
······
-22
who-am-i/src/identity_resolver.rs
-22
who-am-i/src/identity_resolver.rs
···-use atrium_identity::did::{CommonDidResolver, CommonDidResolverConfig, DEFAULT_PLC_DIRECTORY_URL};-let doc = resolver.resolve(&Did::new(did).unwrap()).await.unwrap(); // TODO: this is only half the resolution? or is atrium checking dns?
···
+1
-5
who-am-i/src/lib.rs
+1
-5
who-am-i/src/lib.rs
···
+197
-47
who-am-i/src/oauth.rs
+197
-47
who-am-i/src/oauth.rs
···-// A store for saving state data while the user is being redirected to the authorization server.
···+state: Option<String>, // TODO: we _should_ use state to associate the auth request but how to do that with atrium is unclear
+41
-27
who-am-i/src/server.rs
+41
-27
who-am-i/src/server.rs
···························
···························