Proxy Authentication

[RHeuvel-DICTU]

Hello,

I work for the IT department of the Dutch Ministry of Economic Affairs and Climate Policy and I'm currently tasked with supporting the use of several EFSA applications.

At the moment we are experiencing issues with getting the Data Reporting Tool to connect through our proxy servers. The proxy is returning a '407 Proxy Authentication Required' error code, which suggests that the application is having trouble handling this request or does not support proxy authentication at all.

Could I get in touch with someone who can verify whether the TSE Data Reporting Tool supports proxy authentication and/or help me with further investigation of the issue?

Best regards,

Rowan Heuvel

[AlbSha]

Hello Rowan,

Did you already have a look to the wiki section in which it is described how to set up the proxy configuration manully (here the link)?

Thanks a lot for your feedback.

Kind Regards,
Alban

[RHeuvel-DICTU]

Hi Alban,

Thanks for your reply.

I have configured the proxy both auto and manual. Both settings seem to be working, as the application is communicating with the proxy.

When monitoring the communication on the proxy, we see connections to github-production-release-asset-2e65be.s3.amazonaws.com and dcf-elect.efsa.europa.eu being blocked with the 407 Proxy Authentication Required error code.

Temporarily whitelisting the above addresses bypasses the authorization policy and results in the reporting tool updating and working correctly. I cannot whitelist these permanently however.

While adding the addresses to the whitelist is being discussed, it is also not a solution to the 407 error code, because if the application responds to the authorization request correctly it is allowed to go through the proxy.

Furthermore the Data Reporting Tool is not the only EFSA application that our employees want to use. The Catalogue Browser is facing the same problems.

I hope you can investigate this issue further. Please let me know if you have any questions.

Best Regards,
Rowan

[AlbSha]

Thanks a lot for the complete description of the problem.
I understood perfectly what is the problem and hence we will take some action in order to provide an authentication structure by inserting this header information to the request made by the tool (this will need to be set manually).

As the module has been implemented it will be imported in both the TSE and the Catalogue browser.

Thanks again,
I will come back to you asap on this.

Kind Regards,
Alban

[RHeuvel-DICTU]

Hi Alban,

Thank you again for your quick reply and action. I will look forward to the next update.

Best regards,
Rowan