topic Error while adding credentials in WFA in Active IQ Unified Manager Discussions

Error while adding credentials in WFA

Rutul — Wed, 04 Jun 2025 15:30:55 GMT

I am getting the following error while adding credentials.. Kindly let me know how I can rectify it.

I am able to login to system manager of FAS.

I even setup inbound and outbound rules at WFA server side to allow ports 22,443 and 80. Also tried adding entry in C:\Windows\System32\drivers\etc

Re: Error while adding credentials in WFA

mbeattie — Wed, 01 Feb 2017 01:16:12 GMT

I experienced the same issue in a lab environment and found the root cause was a DNS\Name resolution issue (Not firewall related). My WFA server had multiple network interfaces and I had to ensure the NIC binding order was correct and that it was able to query the DNS server. Ensure you have A and PTR record for the credentials you are adding then try adding it using the FQDN rather than the IP Address.

/Matt

Re: Error while adding credentials in WFA

dkorns — Fri, 10 Feb 2017 00:25:42 GMT

Just to add some additional encounters of this error message ... and my solution.

In my case, the same error was occuring on a WFA 4.1rc1 (Win2012R2) system doing Credential TESTs against a set of clusters where some worked and some did not. The interesting thing was a side-by-side WFA 3.1p2 system could Credentail TEST against all those same systems just fine .. both ONTAP 8.3.2 and all ONTAP 9.0 systems also.

After reading Matt's comment above, I double checked my PTR records in DNS. It turned out that 2 of my ONTAP 9.0 systems DID NOT have reverse lookup PTR records (by accident) and those where the ones failing with the error. Adding the PTR records resolved the problem.

So it appears WFA 4.1rc1 is using a newer protocol option of SSL that requires and depends on PTR records for the clusters. I'm sure a security export could comment with further details ... but PTR reccords are always good to have 🙂 ... but I can imagine lots of lingering configurations out there that are working fine today but uncover this issue when upgrading to WFA 4.x ... caused by some bad DNS practices.