Skip to main content

Set up an OAuth 2.0 HTTP connection to Azure Data Lake Storage Gen2

Comments

4 comments

  • Noppawat Eakpornpith

    Hello Lucien, 

    Thank you for your guideline, it's very helpful.
    I stuck at the authorization part and hope you could give me some guidance. When I finish creating connection and save & authorize, this error occurred. 

    Sorry, but we were not able to successfully authenticate your connection.
    {"code":"invalid_domain","message":"The domain of request url should be present in iClient.oauth2.validDomainNames","source":"resource","resolved":false,"occurredAt":1689331902762}

    I believe the reason is from the Valid domain names input. Unfortunately, your guideline above doesn't say anything about this. Could you please tell me which part I should take a look at so that I can solve this.

    Sincerely,

    Nate

    0
  • Stephen Brandt Documentation Manager Community moderator
    Engaged
    Great Answer
    Top Contributor
    Celigo University Level 3: Master

    Hi, Noppawat Eakpornpith. I looked for a similar problem and resolution and found the following advice:

    Update the Auth url and access token url as per the API documentation i.e, ("https://login.microsoftonline.com/common/oauth2/authorize" & "https://login.microsoftonline.com/common/oauth2/token") and provide the valid domain as "microsoftonline.com".

    If that doesn't help, please reply and we'll get you to some individual support. 

    1
  • Noppawat Eakpornpith

    Hello, Stephen Brandt

    Thank you, it did work for me. It was stupid of me because I put the valid domain like this "iClient.oauth2.microsoftonline.com" while it's supposed to be just "microsoftonline.com".

    By the way, I tried to import JSON data to Azure database and refer to this API DOC Filesystem - Create - REST API (Azure Storage Services) | Microsoft Learn

    Somehow it kept erroring code 400 with message An HTTP header that's mandatory for this request is not specified. Do you happen to have any advise about this case? I tried put request header in the doc to configure HTTP headers in celigo one by one but it still keeps erroring the same code.

    Nate

    0
  • Stephen Brandt Documentation Manager Community moderator
    Engaged
    Great Answer
    Top Contributor
    Celigo University Level 3: Master

    Good to hear, Noppawat Eakpornpith, and thanks for circling back. 

    For your new question, I'm a bit out of my depth, and I wouldn't be able to troubleshoot it without observing or gaining access to your flow. That's best done via a support ticket, if you'll forgive me for the handoff. 

    1

Please sign in to leave a comment.