@aepstore-dev/contracts 1.51.0 → 1.52.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/gen/auth.d.ts +10 -2
- package/gen/auth.ts +10 -2
- package/package.json +1 -1
- package/proto/auth.proto +8 -2
package/gen/auth.d.ts
CHANGED
|
@@ -71,7 +71,7 @@ export interface AuthUser {
|
|
|
71
71
|
* Unified result for login/register/createCode/verifyCode/refresh. Which fields
|
|
72
72
|
* are populated depends on the flow:
|
|
73
73
|
* - fully authenticated → access_token + refresh_token + expires_in + user
|
|
74
|
-
* - 2FA required / pending confirm → message +
|
|
74
|
+
* - 2FA required / pending confirm → message + two_factor_required + two_factor_type + user (no tokens)
|
|
75
75
|
* - totp_generate → secret + otpauth + qr (+ user)
|
|
76
76
|
* - totp_activate → backup_codes (+ tokens/user)
|
|
77
77
|
*/
|
|
@@ -81,7 +81,15 @@ export interface AuthResult {
|
|
|
81
81
|
expiresIn: number;
|
|
82
82
|
user: AuthUser | undefined;
|
|
83
83
|
message: string;
|
|
84
|
-
|
|
84
|
+
/**
|
|
85
|
+
* Renamed from `requires_2fa` in 1.52.0: the digit-after-underscore broke
|
|
86
|
+
* the grpc proto-loader's camelCase pass (`_2` isn't `_<letter>`), so the
|
|
87
|
+
* wire key stayed snake_case and never matched the camelCase handler output
|
|
88
|
+
* → always serialised false. `two_factor_required` camelCases cleanly to
|
|
89
|
+
* `twoFactorRequired` on every layer. Field number 6 is unchanged (wire-
|
|
90
|
+
* compatible).
|
|
91
|
+
*/
|
|
92
|
+
twoFactorRequired: boolean;
|
|
85
93
|
twoFactorType: TwoFactorType;
|
|
86
94
|
/** TOTP setup extras */
|
|
87
95
|
secret: string;
|
package/gen/auth.ts
CHANGED
|
@@ -91,7 +91,7 @@ export interface AuthUser {
|
|
|
91
91
|
* Unified result for login/register/createCode/verifyCode/refresh. Which fields
|
|
92
92
|
* are populated depends on the flow:
|
|
93
93
|
* - fully authenticated → access_token + refresh_token + expires_in + user
|
|
94
|
-
* - 2FA required / pending confirm → message +
|
|
94
|
+
* - 2FA required / pending confirm → message + two_factor_required + two_factor_type + user (no tokens)
|
|
95
95
|
* - totp_generate → secret + otpauth + qr (+ user)
|
|
96
96
|
* - totp_activate → backup_codes (+ tokens/user)
|
|
97
97
|
*/
|
|
@@ -101,7 +101,15 @@ export interface AuthResult {
|
|
|
101
101
|
expiresIn: number;
|
|
102
102
|
user: AuthUser | undefined;
|
|
103
103
|
message: string;
|
|
104
|
-
|
|
104
|
+
/**
|
|
105
|
+
* Renamed from `requires_2fa` in 1.52.0: the digit-after-underscore broke
|
|
106
|
+
* the grpc proto-loader's camelCase pass (`_2` isn't `_<letter>`), so the
|
|
107
|
+
* wire key stayed snake_case and never matched the camelCase handler output
|
|
108
|
+
* → always serialised false. `two_factor_required` camelCases cleanly to
|
|
109
|
+
* `twoFactorRequired` on every layer. Field number 6 is unchanged (wire-
|
|
110
|
+
* compatible).
|
|
111
|
+
*/
|
|
112
|
+
twoFactorRequired: boolean;
|
|
105
113
|
twoFactorType: TwoFactorType;
|
|
106
114
|
/** TOTP setup extras */
|
|
107
115
|
secret: string;
|
package/package.json
CHANGED
package/proto/auth.proto
CHANGED
|
@@ -117,7 +117,7 @@ message AuthUser {
|
|
|
117
117
|
// Unified result for login/register/createCode/verifyCode/refresh. Which fields
|
|
118
118
|
// are populated depends on the flow:
|
|
119
119
|
// - fully authenticated → access_token + refresh_token + expires_in + user
|
|
120
|
-
// - 2FA required / pending confirm → message +
|
|
120
|
+
// - 2FA required / pending confirm → message + two_factor_required + two_factor_type + user (no tokens)
|
|
121
121
|
// - totp_generate → secret + otpauth + qr (+ user)
|
|
122
122
|
// - totp_activate → backup_codes (+ tokens/user)
|
|
123
123
|
message AuthResult {
|
|
@@ -127,7 +127,13 @@ message AuthResult {
|
|
|
127
127
|
AuthUser user = 4;
|
|
128
128
|
|
|
129
129
|
string message = 5;
|
|
130
|
-
|
|
130
|
+
// Renamed from `requires_2fa` in 1.52.0: the digit-after-underscore broke
|
|
131
|
+
// the grpc proto-loader's camelCase pass (`_2` isn't `_<letter>`), so the
|
|
132
|
+
// wire key stayed snake_case and never matched the camelCase handler output
|
|
133
|
+
// → always serialised false. `two_factor_required` camelCases cleanly to
|
|
134
|
+
// `twoFactorRequired` on every layer. Field number 6 is unchanged (wire-
|
|
135
|
+
// compatible).
|
|
136
|
+
bool two_factor_required = 6;
|
|
131
137
|
TwoFactorType two_factor_type = 7;
|
|
132
138
|
|
|
133
139
|
// TOTP setup extras
|