Background Jobs are consuming connections and keeping them in an "idle in transaction" state, leading to exhausted database connections.
<br>
<br>
When the application is idle for more than 10mins and if we perform any action after that we are getting below error message in API.
When we verify the DB, the connections are exhausted.
When we further investigated, we see Background Job manager is opening connections and not closing them.
<br> NPGSQL : 8.0.4 .NET 8 PostgresSQL Version 13.0
Please answer the following questions before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.
We have a functionality where we send an email with the application link to multiple users that will allow them to access the application. We do not want them to go to the login but to the page directly. Could you help us by providing the code to generate the link or any sample which can be used as reference.
Please answer the following questions before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.
We are trying to enable a Single Sign on (SSO) for our application but hit a roadblock. The requirement is the application should work using windows authentication only, if the user is already authenticated/logged into a computer then the application should auto login without requesting user to keyin credentials again. We were able to enable AD(LDAP) authentication in the framework, but it displays the login popup and user need to keyin the credentials to login. Once logged in it work without requesting for the credentials until user clears the browser cache.
Any inputs/suggestions to solve this using configuration/code chage would be greatly appreciated.
