Iron Session Infrastructure Configuration

You can now manage session settings using the Iron Session infrastructure. This update centralizes session management configurations, including cookie parameters and session secret, within the application configuration files, offering a more consistent and reliable approach to handling user sessions.

Session Logout

A "Logout" button is now available in the top right corner of the application header on all authenticated pages. The button uses the Verdant design system with a dark green background and white text, and will end your current session and redirect to the login page when clicked. All session tokens and cookies are cleared upon logout.

Session Persistence and Validation

Authenticated sessions now persist across page reloads. When you are logged in, the application maintains your session, allowing you to navigate and refresh pages without needing to log in again, unless your session expires or you explicitly log out.

Multi-Factor Authentication with Iron Session

Multi-Factor Authentication (MFA) now uses Iron Session during the verification process. When you have MFA enabled, Iron Session manages your session state while you complete the verification steps, adding another layer of security during account access.

Local JAR builds for CDK

You can now generate local JAR files for your CDK projects using the new build command. This action packages your project's compiled source code and dependencies into a JAR file, making it easier to test and deploy CDK applications without requiring remote artifact repositories.

Datadog Telemetry for ECS Fargate Services

ECS Fargate services now include instrumentation with the Datadog library, sending relevant telemetry data directly to Datadog for enhanced monitoring and visibility.

Datadog Telemetry for Lambda Functions

All Lambda functions are now instrumented with the Datadog library via a dedicated construct in the CDK package. This enables telemetry data collection from your serverless workloads automatically. For setup details and customization options, refer to the Datadog documentation.

User Login with Iron Session

You can now log in to your PH360 account using Iron Session. This update provides secure authentication by maintaining your session data in a server-side encrypted cookie whenever you sign in. Once logged in, your session stays active across page refreshes and browser tabs until you log out.

Build System Upgrade

The build architecture now uses Nx and Gradle as the unified engines for managing and compiling all projects. These changes standardize the build process and align support for monorepo environments.

Direct Claude AI Integration via AWS Bedrock

You can now engage directly with Claude AI in the chat interface through a secure connection powered by AWS Bedrock. User messages are sent to Claude, which responds with context-aware answers that appear in your chat. The system tracks the flow of each conversation within a session, displaying coherent, relevant responses, and records essential interaction details like model version, response times, and token usage for monitoring. If an error occurs, you receive a clear on-screen message, ensuring the chat interface remains stable during typical connectivity or service interruptions.

Basic Message Handling

Basic message handling enables you to conduct conversations with PH360 through a chat interface. Your messages are accepted and sent to the AI assistant; responses are returned and immediately displayed, with the entire conversation history preserved so each exchange is understood in context. All messages are saved for record-keeping, and each new conversation session receives a unique identifier. The system also manages common errors, such as when the AI service is temporarily unavailable.

API Scaffolding for Chat System

The initial API scaffolding for the chat system sets up the foundational communication layer between the user interface and backend. This release introduces the standard structure for formatting API requests and responses, a unified approach to error handling, a framework for authenticating users, session tracking for conversations, a health check endpoint for system monitoring, and basic logging to support auditing and compliance. Features such as chat message processing and advanced orchestration are not included at this stage.

PH360 Login Experience API /initiate Endpoint

The /initiate endpoint enables you to start a login session by submitting a user's email or user ID. This triggers the authentication initiation process, returning a session token along with information on the next required authentication steps.

API Endpoint: POST /initiate-authentication

The new POST /initiate-authentication endpoint initiates the authentication process for PH360 users via API. You can trigger a new authentication session by providing required user details in the request body. The endpoint returns a session token and required challenge information to proceed with the next authentication step.

Product Documentation Upload Tool

You can now upload product documentation directly through the documentation site. This includes public links, how-to guides, and reference materials related to your product or service.

AWS Cognito API Integration in Build System

The build system now supports integration with AWS Cognito APIs, allowing you to authenticate users and manage access directly within your application's build pipeline. This integration enables your builds to securely interact with Cognito for tasks such as user sign-in, token refresh, and session validation without requiring external setup.

Login Landing Page

You are greeted with a dedicated login landing page designed for ph360 users. The page guides you through authentication and ensures secure access to your department's PH360 workspace. Prominent fields display clear instructions and feedback, providing a straightforward and welcoming sign-in experience.

Improved Password Management and Account Recovery

Password management now includes clear guidance on security requirements for account creation and updates. Public health workers are prompted to choose passwords that meet established best practices for protecting sensitive information. If you forget your password or lose access to your account, a secure recovery process is available that verifies your identity before allowing account reset. These changes help maintain secure access to PH360 without introducing unnecessary complexity.