INSIGHT-MVP/packages/frontend
Thomas Reitz 1ecd7dad82 fix(ms365): OAuth-Connect via API-Call statt direktem Browser-Link
Problem: <a href="/api/v1/auth/integrations/microsoft-365"> sendet keinen
JWT-Authorization-Header (JWT liegt im Memory, nicht als Cookie).

Lösung:
- Backend: initM365Integration gibt JSON {url} zurück statt server-redirect
- Frontend: integrationsApi.connectM365() ruft Endpoint via Axios ab, dann
  window.location.href zur OAuth-URL
- ProfilePage + EmailsTab + CalendarTab + TasksTab: <a href> → <button onClick>

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-12 22:57:20 +01:00
..
src fix(ms365): OAuth-Connect via API-Call statt direktem Browser-Link 2026-03-12 22:57:20 +01:00
.dockerignore feat: implement Sprint 1 Alpha - full stack with Docker, NestJS, React 2026-03-08 15:33:36 +01:00
Dockerfile feat: implement Sprint 1 Alpha - full stack with Docker, NestJS, React 2026-03-08 15:33:36 +01:00
index.html feat: implement Sprint 1 Alpha - full stack with Docker, NestJS, React 2026-03-08 15:33:36 +01:00
nginx.conf feat: implement Sprint 1 Alpha - full stack with Docker, NestJS, React 2026-03-08 15:33:36 +01:00
package-lock.json feat(crm): Kanban-Board mit Drag & Drop (Phase 3.0) 2026-03-12 22:29:01 +01:00
package.json feat(crm): Kanban-Board mit Drag & Drop (Phase 3.0) 2026-03-12 22:29:01 +01:00
tsconfig.json feat: implement Sprint 1 Alpha - full stack with Docker, NestJS, React 2026-03-08 15:33:36 +01:00
vite-env.d.ts feat: implement Sprint 1 Alpha - full stack with Docker, NestJS, React 2026-03-08 15:33:36 +01:00
vite.config.ts feat(crm): Phase 2.1 Custom Fields — backend + frontend integration 2026-03-12 18:22:57 +01:00