Postgres 14 version has an issue in establishing connection from Axpert
PostgresSQL 14 uses “scram-sha-256” method for authentication by default (as per pg_hba.conf file), which is causing the connectivity issues in Axpert.
Solution for the issue : The method “scram-sha-256” needs to be replaced as “trust” in pg_hba.conf file and refer to the attachments, where both original and changed files are provided as reference.
Related Articles
Error Object reference not set to an instance of an object, when login through axpert developer connecting to postgres
If you experience the below issue when establishing login through axpert developer over browser, it may be due to run schema connection details not available in developer scripts connections. (i.e. axapps.xml)
Axpert Licensing
10.x (9.8 - 10.8) Following are different type of license editions available to use for Axpert versions between 9.8 to 10.8. Evaluation Edition– Allows users to develop and use an app. The app will allow entry of only 500 records in any form in the ...
Error Unable to connect Redis server, when clear In-Memory DB in 11.2.1 Axpert Web
If you experience the below issue when you clear In-Memory DB. It may be due to redis connection not available in axpert configuration. In web config.file, EnableAxpertConfiguration value as "true" For axpert Configuration setting, in web url change ...
Axpert Generic APIs
This document is intended for users who want to consume the restful services provided by Axpert for projects that uses the Axpert as back end. Axpert provides the below services. Login GetIView SaveData. Reference document: AxpertGenericAPI
Migrating dashboard pages from 10.x to Axpert 11
Page builder and Widget builder interfaces are no longer available in Axpert 11 and instead Axpert cards are introduced to display them as widgets in application main page. This article will explain the ways of retaining and maintaining the old ...