Bring back 'active' flag on user creation for BC

schemas/principal-new.json

@@ -14,6 +14,10 @@
       "type": "string",
       "minLength": 3
     },
+    "active": {
+      "description": "Deprecated: If set, and when an identity href is passed when creating a user, this automatically sets that identity as 'verified'. This flag exists to replicate the behavior of older a12n-server versions when email verification was handled through the 'active' flag. This will be fully ignored in a future version and eventually removed.",
+      "type": "boolean"
+    },
     "type": {
       "enum": ["user", "app", "group"]
     }

src/api-types.ts

@@ -162,6 +162,10 @@ export interface PrincipalEdit {
 export interface PrincipalNew {
   _links?: unknown;
   nickname: string;
+  /**
+   * Deprecated: If set, and when an identity href is passed when creating a user, this automatically sets that identity as 'verified'. This flag exists to replicate the behavior of older a12n-server versions when email verification was handled through the 'active' flag. This will be fully ignored in a future version and eventually removed.
+   */
+  active?: boolean;
   type: "user" | "app" | "group";
 }
 /* eslint-disable */

src/user/controller/collection.ts

@@ -49,12 +49,18 @@ class UserCollectionController extends Controller {
       modifiedAt: new Date(),
     });
 
+    if (ctx.request.body.active !== undefined) {
+      console.error('[ERROR] A API client used the "active" flag when creating a new user. This is deprecated behavior!');
+    }
+
     await services.principalIdentity.create({
       principalId: user.id,
       isPrimary: true,
       uri: identity,
       label: null,
-      markVerified: false,
+
+      // Deprecated feature.
+      markVerified: ctx.request.body.active ?? false,
     });
 
     ctx.response.status = 201;