Substituir a interface de depuração de página com a tela de carregamento - Usar o componente LoadingWithOrg existente - Mostrar animação de carregamento elegante durante a validação OTK - Mostrar mensagens de sucesso/erro com redirect automática - Remover todos os painéis de informação de depuração
Implement Redis-based user-info with sliding expiration - Read user data directly from Redis instead of calling SecurityService - Implement sliding session expiration (reset TTL on each read) - Redirect to login site if session expired - Enhanced logging for debugging
Update logout flow to use direct Redis access
Logout Flow Changes: - /logout (page): DELETE Redis session via /api/logout, forward to login/logout - /api/logout: Direct Redis DELETE (no SecurityService call...
FORCE REBUILD: Add extensive logging to /api/validate (Direct Redis)
Critical Change: - This endpoint does NOT call SecurityService - It queries Redis DIRECTLY for OTK validation - Extensive logging added to trace every step New...
Make *** cookie client-accessible & validate OTK directly in Next.js
Major Simplifications: - *** cookie is now client-accessible (httpOnly: false) - Both Next.js and Java can read the cookie directly - Cookie expires in 30 minut...
Fix build error and change *** length to 128 chars
Build Fixes: - Escape apostrophe in validate page (') - Add searchParams dependency to useEffect *** Length Change: - Update expected *** length from 512 ...
Add comprehensive debugging UI to validate page
- Show component render count and validation attempt count - Display OTK information and length validation - Show retrieved *** ID (512 chars) when successful -...
Fix OTK validation duplicate calls issue
- Add useRef to track validation attempts - Prevent duplicate API calls (critical for one-time keys) - Change useEffect deps to empty array (run once on mount) ...
Update OTK validation to use new *** session model
- Extract ***Id from JSON response body (not Set-Cookie header) - SecurityService now returns { success, message, ***Id } - Set *** cookie with 64-char GUID fro...
Add no-cache headers and extensive logging to debug user-info loading
Always call API to fetch user info, don't check HttpOnly cookie client-side
Replace RoleRightType.valueOf with manual lookup of static instances
Use property access instead of method calls for RoleRightType and ServiceType
Extract session ID from upstream and set *** cookie explicitly for internal domain
Update cookie name from KAMOSESH to *** throughout kamo-internal
Implement Redis read/write splitting - writes to master (10.8.0.1), reads from replica
Add checkbox linking feature for preferred names to legal names in profile settings
Remove webpack CSS override that was breaking Tailwind CSS processing
Add missing autoprefixer to PostCSS config - fixes CSS rendering issues
Replace Tailwind v4 with v3 - remove @tailwindcss/postcss, add tailwindcss v3
Fix PostCSS config to use standard Tailwind plugin instead of v4 plugin
Add K2M1 TCP connectivity pre-check with retries
Before attempting kubectl operations, verify TCP connection to 10.8.2.1:6443 - Tests TCP connection 3 times with 5 second delays between attempts - Provides cle...
Add K2M1 secret validation and connection diagnostics
- Validate K2M1_KUBECONFIG_B64 secret exists and is not empty - Show kubeconfig file size for debugging - Add cluster-info test with timeout before deployment -...
Simplify K2M1 workflow to exactly match kamo-login
Removed all continue-on-error flags and debugging code. K2M1 deployment now uses the exact same approach as kamo-login which works. Both servers (K1M1 and K2M1)...
Make K2M1 deployment steps continue-on-error
K2M1 cluster at 10.8.2.1 is not reachable (ping and port 6443 timeout). Adding continue-on-error to all K2M1 steps so builds succeed when K1M1 deploys successfu...
Adicionar conectividade do K2M1 e depuração do kubeconfig
- Adicionar teste de conectividade antes da implantação do K2M1 (ping e verificação de porta) - Adicionar verificações de validação para o segredo K2M1 KUBECONF...
Corrigir a configuração da ligação Redis e da implementação do k8s
- Atualizar o fluxo de trabalho para usar os arquivos de diretório k8s em vez de inline YAML - Restructure ConfigMap para usar chaves individuais env var para o...
Corrigir a configuração do K2M1 kubeconfig usando comandos de configuração do kubectl
Adicionar a implantação do cluster K2M1 ao fluxo de trabalho de compilação e implantação
Como o que vês no transporte?
Cada uma dessas atualizações pousa automaticamente em seu espaço de trabalho. Comece grátis e veja crescer semana após semana.