My Stuff
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
No Limits. Just possibilities.
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
Celebrate Your 2025 Community Recap & Achievements!
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
Staying Connected During the Holidays
Season’s greetings to you and yours! As we head into the holidays (December 24 – January 4), we want to take a moment to celebrate the incredible strength and collaboration within our community. Even during the break, you can continue to benefit from connecting with peers, searching related threads, posting your questions, and marking helpful replies as “Accepted” in the Support Community.
Please note our dedicated team will be on reduced coverage during this time, and regular responsiveness will resume on January 5. Wishing you a joyful and restful holiday season!
-The NetSuite Support Community Team
Season’s greetings to you and yours! As we head into the holidays (December 24 – January 4), we want to take a moment to celebrate the incredible strength and collaboration within our community. Even during the break, you can continue to benefit from connecting with peers, searching related threads, posting your questions, and marking helpful replies as “Accepted” in the Support Community.
Please note our dedicated team will be on reduced coverage during this time, and regular responsiveness will resume on January 5. Wishing you a joyful and restful holiday season!
-The NetSuite Support Community Team
Comments
-
Thank you Erick; modifying the role solved our predicament. It would have been nice had the error stated a bit more than just "invalid_login_attempt".
-
Erick... The documentation you cite above, look at the table underneath "The Access Token Response". That response contains three fields: access_token, expires_in and token_type. The access_token is what is subsequently used. That access_token contains a base64 encoded jwt. I have no control over what fields are inside the…
-
If you try yourself, you'll see that inside "access_token", you will find a base64 encoded string that you can evaluate using jwt.io. It will look something like this: { "sub": "1009;41", // Not sure what this is, but assumes it is connected to the OAuth 2.0 Client Credentials Setup setup "aud": [ "<The integration…
-
JSON Response field named "access_token" is the access token. Hence the name "access_token". ;)
-
We compared both flows and the tokens used. One of those tokens is the access token that was returned after I posted my client_assertion to the token endpoint. The second token was the token we received when we tested the Authorization Code Grant Flow. We wanted to compare these tokens to see if it would provide some clues…
-
Login Audit Trail reports e-mail, company name, ip and 'success'. Integration record: m2m setup: authorized apps: role: Client credentials flow { "sub": "1009;41", // Not sure what this is, but assumes it is connected to the OAuth 2.0 Client Credentials Setup setup "aud": [ "<The integration application id>;<account id>",…
-
POST yields the same result. 401.
-
On a related note: On Saturday I used my client_assertion to acquire an access_token. Today I reran that exact same query. I expected an error saying my client_assertion had expired, but it happily returned an access_token.