@faable/auth-sdk 2.7.4 → 2.7.6

package/dist/api/types.d.ts

@@ -285,7 +285,7 @@ export interface paths {
         };
         /**
          * Resolve the login methods for a client
-         * @description Returns the ordered list of login methods the hosted login screen should offer for this client, already filtered by `connection.enabled` and `connection.enabled_clients`. `client_id` is the OAuth client_id; when omitted it falls back to the account's single client if it has exactly one, otherwise no client context is assumed and only unrestricted connections are returned.
+         * @description Returns the ordered list of login methods the hosted login screen should offer for this client, already filtered by `connection.enabled` and `connection.enabled_clients`. `client_id` is the OAuth client_id; when omitted the server resolves one: the account's only client, or its only client with `callbacks` (the ones that could plausibly be behind a login screen), and failing that the first of those two lists in order. `client` comes back `null` only for an account with no clients at all, and `methods` is always resolved against the client that comes back.
          */
         get: operations["connection/loginOptions"];
         put?: never;
@@ -8908,6 +8908,8 @@ export interface operations {
                         account: {
                             id: string;
                             name: string;
+                            /** @description The tenant's auth host. The login screen talks to this host for every call it makes after the first paint, so it has to come back here: a screen that is served as a static bundle has no other way to learn it, and asking the management API for it is what used to force the hosted UI to hold a platform credential. */
+                            domain: string;
                             logo_src: string | null;
                             icon_src: string | null;
                         };

package/dist/version.js

@@ -9,13 +9,13 @@
 // login pages could not import the SDK at all. Same pattern as auth-js.
 //
 // The sentinels MUST stay byte-identical to the `from` values in `.releaserc`.
-export const version = "2.7.4";
+export const version = "2.7.6";
 // Short git SHA of the released commit. The version dates a build; this names
 // the exact tree, so a canonical log line or an audit entry leads straight to
 // `git show <sha>`. Deliberately NOT hex: an unreleased build (dev, a local
 // link) cannot be mistaken for a real commit — auth only records values that
 // look like a SHA, and this one never will.
-export const commit = "da17046";
+export const commit = "7a7b73e";
 // What this SDK writes in `x-faable-client`. Exported for a consumer that
 // builds a strategy on its own (outside `FaableAuthApi`) and still wants the
 // token request attributed — a bare `authClientCredentials` stamps only what

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@faable/auth-sdk",
-  "version": "2.7.4",
+  "version": "2.7.6",
   "author": "Marc Pomar <marc@faable.com>",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/spec/openapi.json

@@ -3,7 +3,7 @@
   "info": {
     "title": "@faablecloud/auth",
     "description": "Auth Platform made by Faable. Manage Users and Roles",
-    "version": "2.24.0",
+    "version": "2.25.1",
     "license": {
       "name": "private",
       "url": "https://faable.com/docs/platform/privacy-policy"
@@ -14127,7 +14127,7 @@
         "tags": [
           "connection"
         ],
-        "description": "Returns the ordered list of login methods the hosted login screen should offer for this client, already filtered by `connection.enabled` and `connection.enabled_clients`. `client_id` is the OAuth client_id; when omitted it falls back to the account's single client if it has exactly one, otherwise no client context is assumed and only unrestricted connections are returned.",
+        "description": "Returns the ordered list of login methods the hosted login screen should offer for this client, already filtered by `connection.enabled` and `connection.enabled_clients`. `client_id` is the OAuth client_id; when omitted the server resolves one: the account's only client, or its only client with `callbacks` (the ones that could plausibly be behind a login screen), and failing that the first of those two lists in order. `client` comes back `null` only for an account with no clients at all, and `methods` is always resolved against the client that comes back.",
         "parameters": [
           {
             "schema": {
@@ -14177,6 +14177,7 @@
                       "required": [
                         "id",
                         "name",
+                        "domain",
                         "logo_src",
                         "icon_src"
                       ],
@@ -14187,6 +14188,10 @@
                         "name": {
                           "type": "string"
                         },
+                        "domain": {
+                          "type": "string",
+                          "description": "The tenant's auth host. The login screen talks to this host for every call it makes after the first paint, so it has to come back here: a screen that is served as a static bundle has no other way to learn it, and asking the management API for it is what used to force the hosted UI to hold a platform credential."
+                        },
                         "logo_src": {
                           "anyOf": [
                             {