You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Punchin Url to Oracle CPQ using Session Id - SOAP V1 EOL Impact

in Configure Price Quote

Summary:

Hello Team,

Currently we have a scenario whereby Users from an External Application can Create/Modify Quote/Configuration by navigating to CPQ using a System User (Ex: APIUSER) and by navigating using Url in the below format:

https://hostname.bigmachines.com/commerce/transaction/oraclecpqo/1xxx7115xxx?sessionId=d402171f11a548e5aa18d2d8e57f915d4bd288c1e225bd0f3a8b&username=APIUSER&sso=true

The sessionId parameter in the url is set using the login API (passing APIUSER credentials) of Soap V1 Security Web Service. With this approach the External Application user is able to land on the Commerce or Configuration based on the url formation and is logged in using the System User.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!