docs(auth): two Pireon clients, production URLs and sign-in troubleshooting

- Registering clients: the authorization_code client is confidential and needs
  its secret; Pireon shows it once (rotate-secret if lost); containers must be
  recreated to read new environment variables.
- Production URLs (taskstream.pireon.dev, api.taskstream.pireon.dev) and their
  redirect URIs.
- "Si el login falla": each error seen while deploying (not configured,
  unauthorized_client, missing client_secret, invalid_client, redirect URI,
  expired code, wrong credentials, intermittent 404s) with cause and fix.
- READMEs mention both clients; Word/PDF regenerated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-03 16:01:33 +02:00
parent b1002e6599
commit 6c3550ae9d
6 changed files with 36 additions and 5 deletions

View File

@@ -22,4 +22,5 @@ Cada librería de `libs/` tiene además su propio `README.md` con su responsabil
docker compose up -d --build # web en http://localhost:8080
```
Para entrar hace falta un cliente OAuth de Pireon en `.env` (ver [Autenticación](05-autenticacion.md#registrar-taskstream-como-cliente-en-pireon)).
Para entrar hacen falta dos clientes OAuth de Pireon en `.env` (`authorization_code` y `password`, ver
[Autenticación](05-autenticacion.md#registrar-taskstream-como-cliente-en-pireon)).