Feedback
Post-installation verification - Next Gen Identity Server
Next Gen Identity Server should not be deployed during EA except for customers participating in the beta program.
A successful installation produces an ASP.NET Core 10 application running under IIS. The application serves requests at /RIS on the Default Web Site. The Identity application pool runs under the configured service account. It uses no managed runtime. The service exposes a standard OpenID Connect discovery endpoint. It writes a deployment record to the EDDS database. If Environment Watch is configured, the service also emits telemetry to the OpenTelemetry Protocol (OTLP) collector.
Perform all verification steps on the Identity Server host immediately after the installer completes.
Verification steps
Complete the following checks on the Identity Server host immediately after the installer completes.
1. Verifying the Next Gen Identity Server health check
The Next Gen Identity Server exposes two endpoints for health validation:
| Endpoint | Purpose | Components validated |
|---|---|---|
https://[domainname]/RIS/Healthcheck
|
self-check | Verifies that the Next Gen Identity Server application is running and responsive. |
https://[domainname]/RIS/Diagnostics
|
Dependency diagnostics | Validates connectivity to the EDDS database (SQL Server) and the Relativity Secret Store. |
Run both endpoints from a browser on the Next Gen Identity Server host. Use localhost for [domainname]. Then repeat both checks from a client machine using the server's fully qualified hostname. This confirms there are no firewall or DNS issues blocking external access. Identify the failing component and consult the appropriate guide.
2. Verifying the installer exit code
When the installer completes, the exit code is displayed in the terminal. A code of 0 means the installation succeeded. If the terminal shows a non-zero exit code, open the log file specified by your /log parameter and review the entries near the end for the specific failure.
If either health endpoint in step 1 returns an error, see the Troubleshooting Guide for IIS and dependency diagnostics.
3. Verifying the deployment record in EDDS
Run the following query to verify a successful deployment was recorded in EDDS:
Copy
SELECT TOP 1
Name, deploymentData
FROM [EDDS].[eddsdbo].[DeploymentLogs]
WHERE [Name] = 'Identity Server'
ORDER BY Id DESC
Expected: A row appears. The deploymentData column contains JSON - confirm it includes "status": "Install Success" and "metadata": "{"timestamp_utc":"2026-06-24T05:30:03.2082454Z",..} The timestamp_utc shows the install timestamp in UTC.
4. Verifying telemetry (Environment Watch environments only)
Skip this step if Environment Watch is not deployed in your environment.
If Environment Watch is deployed, confirm the Next Gen Identity Server is emitting telemetry:
- Open a browser on the Next Gen Identity Server host and navigate to
https://localhost/RIS/Healthcheckto generate a trace. - Open your Environment Watch dashboard and check for incoming traces and metrics from the source
Relativity.Server.IdentityService.
If no data appears after a few minutes, test connectivity to the OTLP collector from the Next Gen Identity Server host:
Copy
Test-NetConnection -ComputerName <otel-host> -Port 8200
