Discussions
Check out Oracle NetSuite upcoming events and conferences here
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Attention: Customers with NetSuite Electronic Bank Payment (EBP) SuiteApp, version 2020.2 QA (ID 315896) must UPDATE (do NOT uninstall) their bundle to the Production version 2022.1 (ID 416781) by December 31, 2022. Note: If users fail to manually update the Electronic Bank Payments SuiteApp within the given time window, this version of the SuiteApp (ID: 315896) will be deprecated and the account will not be updated to Leading version (2022.1) of the Electronic Bank Payments SuiteApp. Please refer to the campaign email sent to impacted customers for more information.
Update your Profile with your Support type to get your Support Type badge.
NetSuite Release 2023.1 is here! Download the release notes and post your questions in the new Release 2023.1 category.
Join the webinar and "Get the Most Out of NetSuite Inventory Management" on May 2, 2023 at 10 AM PST. Click on this link to register. Do not forget to RSVP on this page as well!
Why am I getting INVALID_LOGIN_ATTEMPT when using aws lambda to call my restlet
I am trying to diagnose an issue with connecting to a RESTlet from AWS lambda. I think I have the user and token role setup correctly as when I reach out with Postman I get the response I expect. On the other hand, when I try to connect from the lambda function I have created in AWS I get an INVALID_LOGIN_ATTEMPT. I see nothing in my 'login audit trail' to help point me in the direction of what is going wrong.
Attached
is the code I have for creating the OAuth header I use in token based authentication. If anyone can help me figure out what the issue is or how to track down the error I would be eternally grateful.
1