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:
@@ -14,8 +14,9 @@ releases, comentarios y relaciones entre tickets, **en tiempo real**.
|
||||
docker compose up -d --build # web en http://localhost:8080
|
||||
```
|
||||
|
||||
Para entrar hace falta un cliente OAuth de Pireon en `.env` (`PIREON_CLIENT_ID` y `PIREON_CLIENT_SECRET`, ver
|
||||
[Autenticación](docs/05-autenticacion.md#registrar-taskstream-como-cliente-en-pireon)). Para desarrollar:
|
||||
Para entrar hacen falta los clientes OAuth de Pireon en `.env`: uno `authorization_code` (`PIREON_CLIENT_ID` /
|
||||
`_SECRET`, «Entrar con Pireon») y uno `password` (`PIREON_PASSWORD_CLIENT_ID` / `_SECRET`, email y contraseña). Ver
|
||||
[Autenticación](docs/05-autenticacion.md#registrar-taskstream-como-cliente-en-pireon). Para desarrollar:
|
||||
|
||||
```sh
|
||||
npm install # @pi/ui necesita el token del Nexus de Pireon en ~/.npmrc
|
||||
|
||||
Reference in New Issue
Block a user