a bad log in user error from postgres means that you were not passing in a correct password or that postgres was not setup to allow connections from your ip address, by changing the authentication method in pg_hba. conf from md5 to trust, you told postgres not to check your password. Which suggests that the bad login error was comming from passing in a wrong password.
The "trust" setting is an opportunity for a fairly comprehensive denial-of-service attack
(unintentional or otherwise) to edit or delete all your data. I strongly suggest that you
protect your data as much as you value it, by using "md5" and a password.
I am seeing this same error in ArcGIS 10.6.1 Enterprise using IWA login and wish to resolve this either on the IT side of the house or in the postgres side. Please advise me on a solution pathway.
he ArcGIS Server service in Windows runs as a task, which has a user associated with it. Does the user that AGS is running as have access to SQL Server? When a data source is published with OS Authentication, then ArcGIS Server would be using it's OS authentication, not the authentication of the user that is publishing it. This is why the database user (arcgis_db) works, but the Windows user does not work. Share