René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Dataikuapi is not correctly honoring \"DKU_NO_CHECK_CERTIFICATE\" in requests","articleBody":"In theory, Dataiku supports using self-signed certificates by setting e.g. using an environmental variable DKU_NO_CHECK_CERTIFICATE or by setting `no_check_certificate=True` in the `set_remote` function call of the non-open source dataiku package.\r\n\r\nHowever, this parameter is not passed to the api_client(), which causes requests to fail which are made to Dataiku instances using self-signed certificates. It is possible to mitigate this by setting the verify value of the internal Session object to false:\r\n\r\n    client = dataiku.api_client()\r\n    client._session.verify = False\r\n\r\nWhich is not obvious and requires looking through the internals of the package.\r\n\r\nA fix at the central call site of the dataikuapi package, `_perform_http`:\r\nhttps://github.com/dataiku/dataiku-api-client-python/blob/fc51e29a12a1f50717771522e1b450ae91ff4d87/dataikuapi/dssclient.py#L1228-L1233\r\nwould only be possible in parts by duplicating the logic to check the \"DKU_NO_CHECK_CERTIFICATE\" variable or config files, but would still fail for Dataiku session set up by using the `set_remote_dss` function call.\r\n\r\nThe best option would be to add a \"no_check_certificate\" parameter to the `DSSClient` class that can be set when creating an instance of the class. But as the `DSSClient` is also used by the closed-source `dataiku` package, it seems to me that this can't be solved by contributing to the open source  `dataikuapi` package.\r\n","author":{"url":"https://github.com/seb-ehm","@type":"Person","name":"seb-ehm"},"datePublished":"2022-06-17T15:52:32.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/243/dataiku-api-client-python/issues/243"}