![]() Verify request - The external application sends back to NetSuite the token, the consumer key, and the signature, along with other information such as the timestamp and nonce, to verify the user. ![]() Using the hard-coded mapping between the dc parameter and the URL might cause problems when your account is moved to a different data center that is missing in your mapping. The outbound HTTP call still includes a dc and an env URL parameters, but you should not use them. If any data fields were previously defined as required context for the connection, NetSuite sends values for these fields at the same time. Send the web services request to the domain specified by the value of the webservicesDomain parameter. Send the verify request to the domain specified by the value of the systemDomain parameter. This outbound HTTP call also includes a systemDomain URL parameter, and a webservicesDomain URL parameter for the optional web services calls. Outbound single sign-on request - NetSuite generates a token, and sends this token to the external application as the value for the oauth_token URL parameter. User clicks on one of the following in the NetSuite user interface:Ī subtab that provides SuiteSignOn accessĪ page displaying a portlet that provides SuiteSignOn accessĪ link for a Suitelet that provides SuiteSignOn accessĪn action button that results in the execution of a user event script that provides SuiteSignOn access User logs in to NetSuite, initiating a NetSuite session. See the following detailed steps for each action shown in the preceding SuiteSignOn connection sequence diagram.
0 Comments
Leave a Reply. |