INSIGHT-MVP/packages/frontend/src/crm/contacts
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
..
CalendarTab.tsx fix(ms365): OAuth-Connect via API-Call statt direktem Browser-Link 2026-03-12 22:57:20 +01:00
ContactDetailPage.module.css feat(crm): remove Lexware section from ContactDetailPage 2026-03-12 20:49:36 +01:00
ContactDetailPage.tsx feat(crm): Phase 3 MS365 Frontend — Integrationen + Kontakt-Tabs 2026-03-12 22:48:43 +01:00
ContactFormModal.tsx feat(crm): UI/UX Redesign – Kontakt Eingabemaske & Detailansicht 2026-03-12 20:20:30 +01:00
ContactsPage.module.css feat: CRM Frontend-Modul mit Kontakte, Deals, Pipelines und Aktivitäten 2026-03-10 19:13:02 +01:00
ContactsPage.tsx feat(crm): add Company module + extend Contact/Deal with company relation 2026-03-10 20:10:58 +01:00
EmailsTab.tsx fix(ms365): OAuth-Connect via API-Call statt direktem Browser-Link 2026-03-12 22:57:20 +01:00
TasksTab.tsx fix(ms365): OAuth-Connect via API-Call statt direktem Browser-Link 2026-03-12 22:57:20 +01:00