Not able to access Virtual Services API in the Registry url

Products

• Service Virtualization

Issue/Introduction

Customer is not able to login to the DevTest Portal using admin, devtest and svuser.

The Registry name is visible at the bottom of the login window.

Enterprise Dashboard is working, however they can't see any VSEs and Power user there.

 

This is the error message:

Authentication failed. Unable to connect to identity and Access manager. Please check with your administrator.

 

Registry log showing this error:

 

Caused by: java.net.UnknownHostException: <server_host_name>: Temporary failure in name resolution

at java.base/java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method) ~[?:?]

at java.base/java.net.InetAddress$PlatformNameService.lookupAllHostAddr(InetAddress.java:934) ~[?:?]

at java.base/java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1543) ~[?:?]

at java.base/java.net.InetAddress$NameServiceAddresses.get(InetAddress.java:852) ~[?:?]

at java.base/java.net.InetAddress.getAllByName0(InetAddress.java:1533) ~[?:?]

Used the curl command from Registry machine to the IAM machine and was not able to connect.

 

Environment

All supported DevTest releases.

On AWS the customer was using 2 Unbound DNS servers. (Unbound is a validating, recursive, caching DNS resolver.)

/etc/unbound/unbound.conf - The unbound.conf file is used to configure the Unbound DNS resolver. (It specifies settings such as the interfaces to listen on, access control rules, caching behavior, and how to handle various DNS queries.)

Cause

The unbound DNS servers were forwarding to IPs that were decommissioned and new servers took their place. This is the reason they needed to change the IP addresses in their unbound.conf file.  They made changes in their environment, and didn't update their config.

Resolution

Once the correct IP addresses were configured in the unbound.conf file, Connectivity from the Workstation, Registry, Portal and VSE to IAM started working.