The method of login is designed to require less configuration and administrative work for the customer. In this case, only the user ids need to be stored individually in the ERP, and a common password is shared by all users. Within this method, there are 3 options (highlighted below) for user authentication but the use of only 1 is required.
<?xml version="1.0"?>
<!DOCTYPE cXML SYSTEM "http://xml.cxml.org/schemas/cXML/1.2.017/cXML.dtd">
<cXML xml:lang="en-US" payloadID="2009091509:00:25.818510504@test.com" timestamp="2009-09-15T09:00:25">
<Header><From><Credential domain="NetworkId">
<Identity>1234</Identity>
</Credential></From>
<To><Credential domain="DUNS">
<Identity>123456789</Identity>
</Credential>
</To><Sender><Credential domain="NetworkId">
<Identity>1234</Identity>
<SharedSecret>SubscriptionPassword</SharedSecret>
</Credential>
<UserAgent>Your System Name</UserAgent>
</Sender></Header>
<Request deploymentMode="test">
<PunchOutSetupRequest operation="create">
<BuyerCookie>buyer_cookie</BuyerCookie>
<Extrinsic name="UserId">123</Extrinsic>
<Extrinsic name="Email">John.Smith@address.com</Extrinsic>
<Extrinsic name="UserEmail">John.Smith@address.com</Extrinsic>
<BrowserFormPost><URL>http://www.wherever.com</URL></BrowserFormPost>
<Contact role="requestor">
<Name xml:lang="en">someone</Name><Email>someone@company.org</Email>
</Contact>
<SupplierSetup>
<URL>https://trng-ws.partsfinder.com/Services/PunchoutSetupService.svc</URL>
</SupplierSetup>
</PunchOutSetupRequest>
</Request>
</cXML>
| <Header><From><Credential><Identity> | This is the customer’s service subscription ID*, as defined by PartsSource. *Subscription ID provided upon setup. |
| <Header><Sender><Credential><SharedSecret> | This is the customer’s subscription password*, as assigned by PartsSource. *Password provided upon setup. |
| <Header><To><Credential><Identity> | PartsSource's DUNS ID*. *DUNS ID provided upon setup. |
| <Request><PunchOutSetupRequest><Extrinsic name="UserId"> |
User Authentication Option 1: The PartsSource Supplied ID for the individual user logged on to the system. Please note that the Extrinsic’s name value must be “UserId” and is case-sensitive. Only 1 of the 4 User Authentication Options is required. |
| <Request><PunchOutSetupRequest><Extrinsic name="Email"> |
User Authentication Option 2: The company email address assigned to the user and supplied to PartsSource during user setup. Please note that the Extrinsic’s name value must be “Email” and is case-sensitive. Only 1 of the 4 User Authentication Options is required. |
| <Request><PunchOutSetupRequest><Extrinsic name="UserEmail"> |
User Authentication Option 3: The company email address assigned to the user and supplied to PartsSource during user setup. Please note that the Extrinsic’s name value must be “UserEmail” and is case-sensitive. Only 1 of the 4 User Authentication Options is required. |
| <Request><PunchOutSetupRequest><Contact><Email> |
User Authentication Option 4: The company email address assigned to the user and supplied to PartsSource during user setup. Only 1 of the 4 User Authentication Options is required. |
| <Request><PunchOutSetupRequest><BrowserFormPost><URL> | This is the URL that ePartsFinder will post the Shopping Cart, via the Punch-out Order Message (POOM) back to when the user is complete with their session. |