Description of problem:
Receiving "Internal Server Error" or "ipa: ERROR: cannot connect to 'any of the
configured servers'" from IPA when performing a non-critical task may imply to
customers that a fully-functional IPA instance is somehow broken


Version-Release number of selected component (if applicable):
RHEL 8.1 / IPA 4.8


How reproducible:
Consistent


Steps to Reproduce:
1. Set up IPA and Establish Trust with an AD domain
2. kinit as an AD user, but do not have them in the "Default Trust View"
3. Perform an IPA command, like `ipa ping`


Actual results:
"Internal Server Error" or "cannot connect to 'any of the configured servers'"
message is displayed


Expected results:
Report a less-general, less-alarming error message like "you do not have
permissions to run this command" so customers know IPA is still working as
expected


Additional info:
1) At one point at IdM Hackfest 2019, we received "Internal Server Error" on a
fresh install when performing `ipa ping` with an unprivileged user, but was
unable to reproduce this afterwards.

2) Received another misleading error:

   [root@replica ~]# kinit Administrator@WIN2016.TEST
   Password for Administrator@WIN2016.TEST:

   [root@replica ~]# id Administrator@WIN2016.TEST
   id: ‘Administrator@WIN2016.TEST’: no such user

   [root@replica ~]# ipa ping
   ipa: ERROR: cannot connect to 'any of the configured servers':
https://replica.ipa.test/ipa/json, https://master.ipa.test/ipa/json