Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Working with databases in Azure Cloud, Microsoft Entra authentication is something that provides a more robust security than plain user/password authentication.
In our scenario it's for a PostgreSQL database but it could be another database type.
Is there anyway of using this authentication method on Qlik Replicate for PostgreSQL?
Hi,
Please open a case for this question so we can check it internally with our suport team.
Thanks & regards,
Orit
Hello @ernesto_costa ,
Would it be possible for you to create a 64-bit ODBC DSN that successfully connects to the PostgreSQL database (or another database) using Microsoft Entra Authentication?
If that works, we can apply the same ODBC parameters to the Qlik Replicate endpoint, and it should work there as well.
Hope this helps.
John.
Hi @john_wang,
haven't been able to create an ODBC DSN using Microsoft Entra Auth.
Have you tried it before? Can you share the details?
Thank you.
Hello @ernesto_costa ,
The detained information can be found in the database webpages, eg for SQL Server UI Additions for Microsoft Entra ID.
Regards,
John.
Hi @john_wang,
thank you for the reply.
That is an option for SQL Server, but my use case is PostgreSQL.
Any information on that scenario?
Hello @ernesto_costa ,
You might want to check with your DBA or PostgreSQL to configure the DSN.
Regards,
John.
Hi @john_wang,
haven't been able to create the DSN.
But in the meantime I created a workaround which involves a scheduled process that retrieves a new token from MS Entra every 50 minutes, updates the endpoint and restarts the task that uses it.
This is fine and it should work.
But forget about the DSN and workaround, I have detected a bigger issue.
When I use the source endpoint in a task with the user and token from Entra, I'm receiving the following error:
I'm able to connect to the database using, for example, Dbeaver without any issue and even testing the connection on Replicate shows that everything is OK with the connection.
When I use a normal user and password, not from Entra, it works fine.
We are using an Azure Database for PostgreSQL flexible server.
Any idea of what the issue might be?