@dacyti-gsi/auth 0.0.0-stage → 0.2.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Carlos Burelo
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -1,3 +1,419 @@
-# Temporary Holding Version
-
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+# @dacyti-gsi/auth
+
+Cliente del Portal SSO. Autenticación OIDC y permisos con la mínima ceremonia.
+
+> **Es el cliente de servidor.** Mantiene el `client_secret` y guarda la sesión
+> en una cookie `HttpOnly`, así que necesita un backend: Next.js, un BFF, un
+> servicio Node. **Un frontend en el navegador no debe usarlo** —no puede
+> guardar un secreto ni una cookie—: se registra en el portal como cliente
+> público (`spa` o `native`, solo PKCE, sin secreto) y usa una librería OIDC
+> estándar contra `https://sso.<tu-dominio>/api/auth`.
+
+## Instalar
+
+```bash
+pnpm add @dacyti-gsi/auth
+```
+
+## Integrar una aplicación Next.js
+
+**1. Declara el cliente**
+
+```ts
+// lib/sso.ts
+import { defineNextSSO } from "@dacyti-gsi/auth/next";
+
+export const sso = defineNextSSO({
+  // Convierte una errata en un error de compilación
+  permissions: ["documentos:crear", "documentos:anular"],
+});
+```
+
+Nada más: `issuer`, `clientId`, `clientSecret` y `secret` salen de
+`SSO_ISSUER`, `SSO_CLIENT_ID`, `SSO_CLIENT_SECRET` y `SSO_SECRET`. Si falta
+alguna, revienta al arrancar diciendo cuál.
+
+**2. Monta las rutas**
+
+```ts
+// app/api/sso/[...sso]/route.ts
+import { sso } from "@/lib/sso";
+
+export const { GET, POST } = sso.handlers();
+export const runtime = "nodejs";
+```
+
+**3. Úsalo**
+
+```tsx
+// app/panel/page.tsx
+import { sso } from "@/lib/sso";
+
+export default async function PanelPage() {
+  const session = await sso.protectPage();
+
+  return <p>Hola, {session.user.name}</p>;
+}
+```
+
+Eso es todo. No hay que escribir PKCE, ni manejar el `state`, ni canjear
+códigos, ni saber que los claims van bajo un espacio de nombres.
+
+## Variables de entorno
+
+```bash
+SSO_ISSUER=https://sso.ejemplo.com/api/auth
+SSO_CLIENT_ID=…
+SSO_CLIENT_SECRET=…
+
+# Cifra la cookie de sesión. Mínimo 32 caracteres.
+# node -e "console.log(require('crypto').randomBytes(32).toString('base64url'))"
+SSO_SECRET=…
+```
+
+Al registrar la aplicación en el portal indica esta URI de redirección:
+
+```
+https://tuapp.com/api/sso/callback
+```
+
+Y, si quieres que cerrar sesión devuelva al usuario aquí, añade también una URI
+de cierre de sesión:
+
+```
+https://tuapp.com/
+```
+
+El portal solo redirige a URIs registradas, así que sin ella la sesión se cierra
+igual pero el navegador se queda en el portal. Si la registras, indícala también
+en `postLogoutRedirectUri`.
+
+## Renovar el acceso (`proxy.ts`)
+
+El acceso dura 15 minutos. Los Server Components no pueden escribir cookies, así que
+sin ayuda cada página renderizada después vuelve a canjear tokens con el portal. Monta
+el proxy una vez por app y la cookie renovada viaja en la respuesta:
+
+```ts
+// src/proxy.ts
+import { sso } from "@/lib/sso";
+
+export const proxy = sso.proxy;
+export const config = {
+  matcher: ["/((?!_next/|api/sso/|favicon.ico|.*\..*).*)"],
+};
+```
+
+Si el portal no responde, no hace nada y la página decide con lo que tenga.
+
+## Robustez
+
+- Toda llamada al portal tiene tope de 10 s: un portal colgado no congela la app.
+- Las rutas `/api/sso/*` responden 503/502 genéricos (el detalle va al log del servidor).
+- Renovaciones simultáneas del mismo refresh token se unifican en una sola llamada.
+- Cada intento de ingreso tiene su cookie (`sso_attempt_<state>`): varias pestañas no se pisan.
+- Si la sesión no cabe en una cookie (~4 KB) falla con un mensaje claro en vez de un bucle de login.
+- `protectPage({ access: true })` deja fuera a quien se autenticó pero no tiene ningún permiso de la app.
+
+## Proteger
+
+```ts
+// Solo exige sesión
+const session = await sso.protectPage();
+
+// Declarativo: permiso + segundo factor + permisos vivos
+const session = await sso.protectPage({
+  permission: "documentos:anular",
+  requireMfa: true,
+  revalidate: true,
+});
+```
+
+Sin sesión, `protectPage()` **redirige** a autenticarse. Con sesión pero sin el
+permiso, **lanza `SSOForbiddenError`**. Sin segundo factor cuando se exige,
+**lanza `SSOMfaRequiredError`**. Son tres situaciones distintas.
+
+```ts
+// app/panel/error.tsx o un try/catch
+import { SSOForbiddenError } from "@dacyti-gsi/auth/next";
+
+if (error instanceof SSOForbiddenError) {
+  // responde 403, no 500
+}
+```
+
+## Server Actions declarativas
+
+```ts
+// app/panel/actions.ts
+export const anularPedido = sso.action("documentos:anular", async (session, id: string) => {
+  // sesión ya autorizada con permisos vivos (revalidate por defecto)
+});
+```
+
+`action()` revalida por defecto: las escrituras consultan al portal en el
+momento. Solo lectura barata usa `{ revalidate: false }`.
+
+Sin sesión, sin permiso o sin segundo factor, lanza por defecto —lo correcto
+para páginas y rutas. Para formularios con `useActionState`, `onDenied`
+convierte la denegación en valor. Un fallo del portal nunca se convierte:
+una caída no es una denegación.
+
+```ts
+export const anular = sso.action("documentos:anular", run, {
+  onDenied: (error) => ({ ok: false as const, message: "Sin permiso." }),
+});
+```
+
+## Componentes RSC
+
+Salen del cliente, ya atados a él y con el catálogo de permisos tipado:
+
+```tsx
+// lib/sso.ts
+export const sso = defineNextSSO({ permissions: ["documentos:ver", "documentos:anular"] });
+export const { Can, SignedIn, SignedOut, SignInLink, SignOutLink } = sso.components;
+```
+
+```tsx
+<SignedOut>
+  <SignInLink returnTo="/panel">Entrar</SignInLink>
+</SignedOut>
+
+<SignedIn>
+  <SignOutLink>Salir</SignOutLink>
+</SignedIn>
+
+<Can permission="documentos:anular" fallback={<p>Sin acceso.</p>}>
+  <BotonAnular />
+</Can>
+
+<Can permission={["documentos:ver", "documentos:anular"]} mode="all" requireMfa>
+  <Auditoria />
+</Can>
+```
+
+- `Can` (alias `Protect`): niega por defecto —sin permiso pintan `fallback` o
+  nada. Nunca redirigen ni lanzan. Para páginas completas usa `protectPage()`,
+  que redirige a entrar.
+- `SignedIn` / `SignedOut`: según haya sesión o no.
+- `SignInLink` / `SignOutLink`: enlaces de entrada (con vuelta) y salida
+  (local y portal). Son Server Components sin JS: solo un `<a>` bien armado.
+
+Las versiones sueltas de `@dacyti-gsi/auth/react` (`<Can sso={sso} …>`) siguen
+existiendo, pero lo normal es usar las atadas.
+
+## Configuración fail-fast
+
+El cliente valida al crearse: `issuer` https (http solo localhost), `secret` de
+32+, catálogo sin vacíos ni duplicados, `basePath` con `/` inicial. Un
+error de configuración revienta al arrancar, no en el primer login.
+
+La cookie es `__Host-sso_session` por defecto (`Secure`, `HttpOnly`,
+`SameSite=Lax`, `Path=/`). Rompe sesiones previas una vez: salida y entrada.
+
+## Leer sin exigir
+
+```ts
+const session = await sso.session(); // SSOSession | null
+
+if (session?.can("documentos:anular")) {
+  // …
+}
+```
+
+## Que un cambio de rol surta efecto ya
+
+`session()` lee la cookie: es un descifrado local, sin red, y por eso los
+permisos son la foto del momento en que se autorizó la aplicación. Si un
+administrador retira un rol, esa foto sigue diciendo lo mismo hasta que
+caduque.
+
+Para las operaciones donde eso no vale, pide permisos vivos:
+
+```ts
+// Una ida y vuelta al portal. Renueva el access token si caducó y vuelve a
+// resolver los permisos.
+const session = await sso.protectPage({ permission: "documentos:anular", revalidate: true });
+```
+
+`revalidate` cuesta una llamada, así que no es el valor por defecto. Ponlo en
+las pantallas y acciones que dependen de un permiso concreto —anular, pagar,
+borrar— y deja el resto en el camino rápido. `action()` ya revalida por
+defecto.
+
+Además, si el portal responde que la credencial ya no vale —token revocado,
+cliente desactivado, cuenta bloqueada— la sesión se da por terminada y
+`protectPage()` vuelve a mandar a autenticarse. Un fallo de red o un 502 del
+portal, en cambio, cae a la foto local: no son motivo para echar a nadie.
+
+**Lo que `revalidate` no hace:** cerrar la sesión *en el portal* no apaga la
+sesión local de tu aplicación. Son sesiones distintas y no hay cierre de sesión
+en segundo plano; la copia local vive hasta `sessionMaxAge`. Si eso importa,
+revalida en las operaciones sensibles o baja `sessionMaxAge`.
+
+## Renovar el acceso
+
+El `access_token` dura quince minutos. Pasados, cualquier llamada a una API con
+`session.accessToken` responde 401 aunque la cookie siga viva.
+
+```ts
+if (session.isExpired()) {
+  // Renueva desde una Server Action declarada, o navega a la ruta del SDK:
+  const renovar = sso.action({}, async () => {});
+  // o un enlace a sso.refreshPath("/panel")
+}
+```
+
+- **`sso.action()`** revalida y persiste la cookie nueva. Es el camino para
+  Server Actions y mutaciones.
+- **`refreshPath(returnTo)`** apunta a la ruta del SDK que renueva, guarda la
+  cookie y devuelve al usuario. Sirve desde cualquier sitio, incluido un enlace.
+- **`resolveSession(cookie)`** es la versión de bajo nivel, para otros
+  frameworks: devuelve `{ session, cookie }` y decide tú dónde guardarla.
+
+Todo esto solo funciona si la autorización pidió el scope `offline_access`, que
+el SDK incluye por defecto. La aplicación tiene que tenerlo permitido en el
+portal: si no, el canje del código responde `invalid_scope`.
+
+## La sesión
+
+```ts
+session.user.id            // identificador estable — úsalo como clave
+session.user.email
+session.user.emailVerified
+session.user.name
+
+session.roles              // ["gerente"]
+session.permissions        // ["documentos:anular", "documentos:crear"]
+session.amr                // ["pwd", "otp", "mfa"]
+
+session.can("documentos:anular")
+session.canAll("documentos:crear", "documentos:anular")
+session.canAny("documentos:crear", "informes:ver")
+session.requires("documentos:anular")   // lanza SSOForbiddenError
+
+session.usedSecondFactor()          // true si amr incluye "mfa"
+session.isExpired()                 // true si el access token ya caducó
+```
+
+## Permisos tipados
+
+El portal define los permisos y tu aplicación les da significado al exigirlos.
+Esta lista es el espejo para TypeScript —declara primero en la consola del
+portal— y con ella los nombres se comprueban al compilar:
+
+```ts
+export const sso = defineNextSSO({
+  // …
+  permissions: ["documentos:crear", "documentos:anular"],
+});
+
+session.can("documentos:crear");   // ✔
+session.can("documentos:crea");    // ✘ error de compilación
+```
+
+Sin esa lista todo sigue funcionando, pero una errata devuelve `false` en
+silencio en producción en lugar de fallar al compilar. El SDK nunca valida la
+forma de un permiso: el portal acepta cualquier cadena opaca y lo que no está
+declarado ahí, simplemente nunca llega en la sesión.
+
+## Exigir segundo factor
+
+```ts
+const session = await sso.protectPage({ permission: "documentos:anular", requireMfa: true });
+```
+
+## Enlaces
+
+```tsx
+<a href={sso.signInPath("/panel")}>Entrar</a>
+<a href={sso.signOutPath()}>Salir</a>
+```
+
+`signOutPath()` cierra la sesión local **y** la del portal. Cerrar solo la local
+dejaría a la persona dentro del portal, y el siguiente `signIn` la devolvería sin
+pedir nada.
+
+Cerrar la sesión del portal exige que la aplicación esté registrada con
+`enable_end_session` y con al menos una URI de cierre de sesión. Ambas cosas las
+pone el portal al registrar la aplicación desde la consola.
+
+## Fuera de Next.js
+
+El núcleo no depende de ningún framework:
+
+```ts
+import { defineSSO } from "@dacyti-gsi/auth";
+
+const sso = defineSSO({ issuer, clientId, clientSecret, secret });
+
+// En tu router, para cualquier ruta bajo /api/sso/
+const response = await sso.handleRequest(request); // Response | null
+
+// Con el valor de la cookie
+const session = await sso.readSession(cookieValue);
+```
+
+`handleRequest` devuelve `null` si la ruta no le compete, para que puedas
+encadenarlo con el resto de tu enrutado. Las rutas que atiende son `sign-in`,
+`callback`, `sign-out` y `refresh`.
+
+`resolveSession` es la que habla con el portal: renueva el acceso caducado,
+vuelve a resolver los permisos si le pasas `revalidate` y te devuelve la cookie
+nueva para que la guardes donde guardes la tuya.
+
+```ts
+const resolved = await sso.resolveSession(cookie, { revalidate: true });
+// resolved === null  →  la sesión terminó
+// resolved.cookie    →  guárdala; `null` si nada cambió
+```
+
+## Opciones
+
+| Opción | Por defecto | |
+|---|---|---|
+| `issuer` | — | **Obligatoria** |
+| `clientId` | — | **Obligatoria** |
+| `clientSecret` | — | **Obligatoria** |
+| `secret` | — | **Obligatoria.** Mínimo 32 caracteres |
+| `permissions` | — | Espejo del catálogo del portal, solo para tipado |
+| `basePath` | `/api/sso` | Dónde montas los handlers |
+| `appUrl` | se deduce | Indícala si el proxy no reescribe `X-Forwarded-Host` |
+| `postLogoutRedirectUri` | — | A dónde vuelve el navegador tras cerrar sesión. Debe estar registrada en el portal |
+| `scopes` | `openid profile email offline_access` | |
+| `cookieName` | `__Host-sso_session` | |
+| `sessionMaxAge` | 7 días | Sesión local, en segundos |
+
+## Qué hace por dentro
+
+- **PKCE `S256` obligatorio.** Verifier de 48 bytes, challenge SHA-256.
+- **`state` comprobado en tiempo constante.** Sin esa comprobación, un tercero
+  puede forzar a alguien a completar un flujo que empezó él, y acabar con la
+  sesión del atacante iniciada en el navegador de la víctima.
+- **Cookie de sesión cifrada** (AES-256-GCM), no solo firmada: contiene el access
+  token, y una cookie firmada es legible por cualquiera que la tenga delante.
+- **El destino tras entrar solo puede ser una ruta de tu aplicación.** Se
+  rechazan las URLs absolutas, las relativas al protocolo y las barras
+  invertidas.
+- **Los claims se localizan por sufijo**, así que no hay que configurar el
+  dominio del portal ni actualizarlo si se mueve.
+- **La cookie temporal del intento se borra al usarla.**
+- **El `id_token` se guarda** porque el cierre de sesión del portal lo exige.
+- **El access token se renueva solo** cuando se pide con `revalidate`.
+
+## Limitación conocida
+
+Los permisos llegan en `/oauth2/userinfo`, no en el token. El SDK los pide en el
+callback y los guarda en la sesión local.
+
+**Consecuencia:** por defecto, un cambio de rol no se ve hasta que la sesión
+local se renueve —hasta `sessionMaxAge`—. Para las operaciones que dependen de un
+permiso concreto, usa `protect(permiso, { revalidate: true })`, que consulta al
+portal en ese momento.
+
+## Licencia
+
+Apache-2.0. El código fuente del cliente vive en
+[dacyti-gsi/auth](https://github.com/dacyti-gsi/auth) y el del portal en
+[dacyti-gsi/sso](https://github.com/dacyti-gsi/sso).