Christopher, It has been a while since I looked at this with Salesforce. I'd think you should be able to set a request or session scope variable and then modify the generated envelope to read that attribute. For Content Server - Content Web Services with SOAP that is the same thing for SOAP based session authentication, it just doesn't have 2 endpoints.
Best, Tim On Wednesday, October 9, 2013 2:28:45 AM UTC-4, Christopher Wennhold wrote: > > Hi Tim, > > I thought about this as a workaround, but would have never imagined, > somebody would really use it. Thanks for your reply, it is working indeed. > Getting subsequent requests to be executed successfully is a little tricky > in a way that you have to define your own envelopes to be able to include > the sessionId, retrieved from the authentication request. > > However, the connectors work fine now. > > Best regards, > > Christopher > -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/reddot-cms-users. For more options, visit https://groups.google.com/groups/opt_out.
