title: Product Updates category: System & Maintenance tags: updates, upgrade, version, patches, release-notes priority: Normal
Product Updates
The Updates page at /admin/updates provides a built-in mechanism to check for, download, and apply IdentityCenter updates. The UpdateCheckerService periodically checks for new versions, and the UpdateDownloadService handles downloading update packages.
Accessing the Updates Page
Navigate to Updates from the System Center or the main administration menu. The page is divided into two sections: the main content area (current version and available updates) and the configuration sidebar.
Current Version Information
The Updates page displays:
| Field | Description |
|---|---|
| Current Version | The installed version of IdentityCenter |
| Last Checked | Timestamp of the most recent update check |
| Status | "You're up to date!" or details of an available update |
Checking for Updates
Automatic Checks
The UpdateCheckerService runs on a configurable interval:
| Setting | Description | Default |
|---|---|---|
| Auto-Check Enabled | Whether to check automatically | Enabled |
| Check Interval | Hours between automatic checks | Configurable in settings |
| Manifest URL | URL of the update server hosting version manifests | Configured during installation |
| Download Path | Local directory for downloaded update packages | Configured in application settings |
Manual Check
Click Check for Updates to immediately query the update server. The button shows a spinner while the check is in progress. If the check fails (e.g., network issue), an error message is displayed with details.
Available Updates
When a new version is available, the Updates page shows:
| Field | Description |
|---|---|
| Version Number | The new version (e.g., v1.2.0) |
| Release Date | When the update was published |
| Critical Badge | Red "CRITICAL" badge if the update addresses security vulnerabilities |
| Release Notes | Detailed description of changes, fixes, and new features |
| File Size | Size of the update package |
Downloading an Update
- Review the release notes to understand what the update includes
- Click Download to begin downloading the update package
- A progress bar shows download status (percentage and bytes transferred)
- Cancel the download at any time with the Cancel button
- When complete, the page shows the local file path of the downloaded package
Applying an Update
After downloading, follow these steps to apply the update:
- Stop the IdentityCenter application or service
- Extract the downloaded ZIP to the installation directory, overwriting existing files
- Start the application -- database migrations will apply automatically on startup
The DatabaseMigrationService detects any new migration scripts included in the update and applies them in order during application startup.
Pre-Update Checklist
Before applying any update, complete this checklist:
| Step | Action | Why |
|---|---|---|
| 1 | Back up the database | Enables rollback if the update causes issues |
| 2 | Back up the application directory | Preserves current binaries and configuration |
| 3 | Review release notes | Understand breaking changes, new requirements, and deprecated features |
| 4 | Check system requirements | New versions may require updated .NET runtime or SQL Server version |
| 5 | Test in staging | Apply the update to a non-production environment first |
| 6 | Verify no jobs are running | Check the Processing Center for active jobs |
| 7 | Notify users | Inform administrators of the planned maintenance window |
Post-Update Verification
After applying an update and restarting the application:
| Verification | How to Check |
|---|---|
| Schema migration | Visit /admin/updates and verify the database schema version matches the application version |
| Service health | Check the System Center for all components showing healthy status |
| Connection status | Verify all directory connections are still connected |
| Sync test | Run a manual sync on one project to verify sync engine functionality |
| Policy evaluation | Trigger a policy evaluation to verify the compliance engine |
| Email delivery | Send a test email from System Center to verify SMTP |
| Report generation | Run a built-in report to verify the reports engine |
| ChatHub | Test a query in the AI Chat to verify LLM integration |
Database Schema Version
The right sidebar of the Updates page shows database schema information:
- List of applied migrations with version, name, and date
- Current schema version
- Migration status indicators (green checkmark for applied, yellow for pending)
This helps verify that all expected migrations have been applied after an update.
Configuration
The configuration panel displays the current update settings:
| Setting | Description |
|---|---|
| Auto-Check | Enabled or Disabled |
| Check Interval | Frequency of automatic checks (in hours) |
| Update Server | URL of the manifest endpoint |
| Download Path | Local directory where updates are saved |
These settings are configured in the application settings file and displayed here for reference.
Rollback Procedures
If an update causes issues:
- Stop the IdentityCenter application
- Restore the application directory from your pre-update backup
- Restore the database from your pre-update SQL Server backup
- Start the application with the previous version
- Verify functionality using the post-update verification checklist
Tip: Database migrations are forward-only. If a migration has already run, restoring the application files alone is not sufficient -- you must also restore the database to the pre-migration state.
Best Practices
- Always back up first -- Create a full database backup and application directory backup before every update
- Test in non-production -- Apply updates to a staging environment before production
- Review breaking changes -- Release notes may call out changes to configuration, APIs, or behavior
- Schedule a maintenance window -- Apply updates during off-peak hours when users are not actively using the system
- Verify after updating -- Complete the post-update verification checklist before considering the update successful
- Keep one version behind -- If your environment is risk-averse, wait one release cycle before adopting new versions (except for critical security updates)
- Monitor after updates -- Watch job success rates and system performance for 24-48 hours after an update
Next Steps
- System Center -- Monitor system health after applying updates
- Database Maintenance -- Understand the migration system and schema management
- Processing Center -- Verify job execution after updates
- Common Issues -- Troubleshoot post-update problems
- Installation & Setup -- Reference for system requirements