2 commits

Author	SHA1	Message	Date
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
Thomas Reitz	30c4b208d9	feat(crm): Phase 3 MS365 Frontend — Integrationen + Kontakt-Tabs ... - Neuer "Integrationen"-Tab in ProfilePage mit "Microsoft 365 verbinden"- Button, OAuth-Callback-Handling (?integration=...&status=...), Trennen-Button - EmailsTab, CalendarTab, TasksTab fuer ContactDetailPage (via MS Graph Proxy) - useIntegrations, useDisconnectM365, useContactEmails/Calendar/Tasks Hooks - integrationsApi + graphApi in crm/api.ts - M365Email, M365CalendarEvent, M365Task, UserIntegration Types in crm/types.ts - Tabs nur sichtbar wenn Kontakt eine E-Mail-Adresse hat; ohne Verbindung Connect-Button Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-03-12 22:48:43 +01:00