Power Automate Oracle NetSuite Integration – OAuth 1.0 “Invalid Login” Error

(0) Share

Report

Posted on by Taher1

Hi Community,

I am working on a Power Automate Flow to integrate with Oracle NetSuite. The requirement is to retrieve data using OAuth 1.0 authentication.
I have implemented the flow with HTTP action, providing all required authentication details (consumer key, consumer secret, token ID, token secret, account ID, signature method, and timestamp).
However, when I run the flow, I get the error: “Invalid Login”.
To troubleshoot, I tested the same API request in Postman with OAuth 1.0, and it works perfectly – I am able to authenticate and fetch the data.
The issue seems to be specific to Power Automate’s handling of OAuth 1.0 requests.
I have followed following blog for implementing this solution.
How to Connect to NetSuite from Microsoft Power Automate using OAuth 1.0 ? | by Anubhav Chaturvedi | Medium

Questions for the community:

Has anyone successfully implemented NetSuite OAuth 1.0 authentication in Power Automate?
Is there a recommended way to configure the signature base string and OAuth headers correctly in Power Automate?
Do I need to use a Custom Connector instead of the HTTP action for OAuth 1.0?
Any Microsoft or Oracle documentation specific to handling OAuth 1.0 with Power Automate that could help?

Any guidance, examples, or references would be really helpful
Thanks in advance!

Categories:

Building flows

NetSuite Integrat...

I have the same question (0)

All responses (3)

Answers (0)

ProPosia 54 on at

Like (0)

Report
Power Automate’s HTTP action doesn’t sign OAuth 1.0a for you. Postman works because it auto-builds the signature. In Power Automate you must generate the full Authorization: OAuth … header yourself (HMAC-SHA256, nonce, timestamp, realm, percent-encoding) and then pass it as a raw header or avoid OAuth 1.0 by using NetSuite’s OAuth 2.0 for REST Web Services.
https://learn.microsoft.com/en-us/answers/questions/1100905/how-to-set-the-headers-for-oauth-signature-method
https://learn.microsoft.com/en-us/connectors/custom-connectors/connection-parameters?
https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_158332610742.html?

Use account-specific domains.

Call the account URL (e.g., https://<ACCOUNT>.suitetalk.api.netsuite.com/... or https://<ACCOUNT>.restlets.api.netsuite.com/...). Generic *.netsuite.com hosts can fail auth.
https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1546938065.html
https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1498251763.html

Build the OAuth 1.0a header exactly as NetSuite expects.

Signature method: HMAC-SHA256 (SHA-1 is no longer supported).

Percent-encode per RFC 5849; mis-encoding → INVALID_LOGIN_ATTEMPT.

Include oauth_realm="<ACCOUNT_ID>" and ensure nonce/timestamp are unique and current (seconds).

Base string = METHOD & base URL & normalized params (incl. query params).
NetSuite shows the required header format & encoding rules.

Generate the header outside the flow, then call NetSuite.

Use a tiny Azure Function/Logic App to output the signed header (Node’s oauth-1.0a, PowerShell, etc.). In your flow:

Step A: HTTP → your function → returns the Authorization string.

Step B: HTTP → NetSuite endpoint, add Authorization header = output from Step A.

Example repo doing exactly this for Power Automate: Azure Functions OAuth 1.0 Authorization Header Generator.
https://github.com/elliott-liu/azure-functions-oauth-1.0?

Role & TBA checks (common cause of “Invalid Login”).
Ensure TBA is enabled and the token’s role has Log in using Access Tokens, User Access Tokens, and the correct Web Services / RESTlet permissions.

Postman parity tips (if Postman works but Flow fails):
Match Postman’s advanced options like “Encode parameters in Authorization header” and (when required) “Add empty parameters to signature.” These affect the signed base string.

Was this reply helpful? Yes No
Taher1 8 on at

Like (0)

Report
I have tried the mentioned approaches, but it is still showing "Invalid Login." The available solutions for this issue are outdated, and there is no proper documentation regarding the integration of Power Automate with NetSuite provided by either Oracle NetSuite or Microsoft.

I have configured the NetSuite integration as follows:

Created an integration and selected TBA.

Generated Consumer ID and Consumer Secret.

Verified that I have Admin access for my role.

Generated Access Token ID and Token Secret.

Created an Azure Function.

Built a Power Automate flow with the required parameters.

Configured the HTTP request to get the signature using HMAC-SHA256.

Created a variable to build the Authorization header, including the generated signature and other parameters.

However, despite these steps, I am still receiving an "Invalid Login" error (screenshot attached)

I followed following blog to implement.
How to Connect to NetSuite from Microsoft Power Automate using OAuth 1.0 ? | by Anubhav Chaturvedi | Medium

Requesting further guidance, Thank you.

Was this reply helpful? Yes No
CU16100322-0 2 on at

Like (0)

Report
Hi ,

I am also trying to setup the same in my environment and may I know what is the redirect URI for for creating a new integration in NS ?

This step

-

Created an integration and selected TBA.

Thanks

Was this reply helpful? Yes No