Roche RIS Feedback Portal

Context

Currently, the connection configuration module in the navify POC Operations user interface (UI) restricts the host address field strictly to static IP address formats. To point a connection to a domain name, we must currently perform a manual workaround by executing an UPDATE statement directly on the corresponding database table.

The Problem

This limitation prevents native compatibility with modern enterprise infrastructures. Many clients operate within cluster environments (such as Kubernetes, cloud-native services, or behind load balancers) where IP addresses are dynamic and change frequently Relying on a static IP causes the connection to break whenever the client's cluster reassigns its nodes, leading to avoidable service downtime.

Proposed Solution

Modify the validation logic in the UI configuration form to accept both standard IP addresses and Fully Qualified Domain Name (FQDN) or DNS alias strings.

• The input field should allow standard network alphanumeric characters and periods (.).

• The backend component handling the connection must perform dynamic name resolution (DNS lookup) at runtime, rather than caching or forcing a hardcoded IP address.