SuiteTalk (Web Services) Platform Guide - NetSuite

Web Services SecurityAuthentication78• When sending user credentials in the SOAP header for an integrated application thathas an application ID assigned, users must submit the application ID with everyrequest. Users will also be responsible for handling SOAP faults related to exceededrequest limits, since they are presumably not synchronizing access to the session.• As with any request (sent after login is invoked or sent with user credentials in theSOAP header), only one Web services request may be in flight at a time. Any attemptto violate this will result in a SOAP fault.Important: Users who choose to authenticate to NetSuite using the login operation donot need to provide their credentials in the SOAP header, and can continueto manage their sessions as they have in the past. For information onauthentication through login, see Authentication Using the Login Operation.The following samples show users credentials as they appear in the SOAP header of a request.Also provided is the Java that generated the SOAP.SOAP Requestjdoe@netsuite.commypassword000034Javaprivate void setRequestLevelCredentials(NetSuitePortType aPort, String sEmail, String sPassword,String sAccount, int iRole) throws SOAPException{NetSuiteBindingStub stub = (NetSuiteBindingStub)aPort;stub.clearHeaders();org.apache.axis.message.SOAPHeaderElement passportHeader = neworg.apache.axis.message.SOAPHeaderElement("urn:messages_2008_2.platform.webservices.netsuite.com","passport");}// use the Passport object to create credentials and add to soap headerRecordRef role = new RecordRef();role.setInternalId(String.valueOf(iRole));Passport passport = new Passport();passport.setEmail(sEmail);passport.setPassword(sPassword);passport.setAccount(sAccount);passport.setRole( role);passportHeader.setObjectValue(passport);// set header on stub, and disable session managementstub.setHeader(passportHeader);stub.setMaintainSession(false);SuiteTalk Platform Guide