1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
//! Models for the `login` resource group.
//!
//! Derived from the Nordnet `ApiKeyLoginResponse`, `Feed`, and
//! `LoggedInStatus` schemas.
//!
//!
//! ## Related types in [`crate::auth`]
//!
//! The auth-flow request and intermediate response types
//! ([`crate::auth::ApiKeyStartLoginRequest`],
//! [`crate::auth::ApiKeyVerifyLoginRequest`],
//! [`crate::auth::ChallengeResponse`]) live alongside the signing
//! primitives in [`crate::auth`] — they are the inputs the signing
//! helpers consume and produce, so the spec keeps them next to
//! [`crate::auth::sign_challenge`] / [`crate::auth::parse_private_key_openssh`].
//!
//!
//! ## Canonical [`ApiKeyLoginResponse`]
//!
//! This is the single canonical [`ApiKeyLoginResponse`] for the workspace.
//! Older revisions of the codebase shipped a loose duplicate in
//! [`crate::auth`] with `private_feed` / `public_feed` typed as
//! `Option<serde_json::Value>`. That duplicate has been deleted in favor
//! of this fully-typed version. Build a [`crate::auth::Session`] via
//! [`ApiKeyLoginResponse::to_session`] when attaching to an HTTP client.
use crateSession;
use ;
/// Connection information for one of the streaming feeds.
/// Response body from `POST /login/verify`.
/// `&ApiKeyLoginResponse` → [`Session`]. Equivalent to
/// [`ApiKeyLoginResponse::to_session`]; provided so callers can use the
/// standard `Into`/`From` conversion idiom.
/// Response body from `PUT /login` (refresh) and `DELETE /login` (logout).