You can translate the question and the replies:

Connection of ADLS container with Denodo on-prem dev server. Error while creating the base view.

Error : There was an error while creating this base view: Error while executing custom wrapper method 'getSchemaParameters': Error accessing DFS file: AADToken: HTTP connection failed for getting token from AzureAD. Http response: 400 Bad Request Content-Type: application/json; charset=utf-8 Content-Length: 419 Request ID: a8e66463-f86d-4148-977f-c75264bafd00 Proxies: none First 1K of Body: {"error":"invalid_request","error_description":"AADSTS901002: The 'resource' request parameter is not supported.\r\nTrace ID: a8e66463-f86d-4148-977f-c75264bafd00\r\nCorrelation ID: 0e1f3a63-dfd9-497a-86b3-dab97b7ecc0d\r\nTimestamp: 2022-03-26 15:32:48Z","error_codes":[901002],"timestamp":"2022-03-26 15:32:48Z","trace_id":"a8e66463-f86d-4148-977f-c75264bafd00","correlation_id":"0e1f3a63-dfd9-497a-86b3-dab97b7ecc0d"}
26-03-2022 11:33:16 -0400

1 Answer

Hi, In this scenario, I would double check the **endpoint URLs** in **core-site.xml** file. The error description ‘**AADSTS901002**’ suggests that the request parameter **‘resource’ is not supported** resulting in 'HTTP response: 400 Bad request'. I presume the ADLS you are trying to connect is V2.0 (Gen 2) which **supports scopes, not resources**. In this case, I would suggest you to avoid **v2.0** reference in the endpoint URLs. e.g. * Use: *https://* * Instead of: *https://**v2.0**/authorize* Please refer to the article [Scopes, not resources]( for detailed information. Additionally, refer [Azure Data Lake Storage]( & [Azure Data Lake Storage Gen 2]( section in the 'Denodo Distributed File System Custom Wrapper - User Manual' for detailed information on configuring authentication properties. Hope this helps!
Denodo Team
28-03-2022 04:38:20 -0400
You must sign in to add an answer. If you do not have an account, you can register here