Hello list, We are currently using a WSOpentTalk SOAP service to integrate with one of our customer web services. The tests were going well, but in the meantime, an additional requirement has popped up: the service should go through a proxy using basic HTTP authentication instead of communicating directly with the final WS endpoint. Is there support for this in VW 7.7? Any help appreciated. Kind Regards, Philippe _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
To provide Http authentication you need to switch from Opentalk client to WsdlClient and use #transportClient (HttpClient) to set proxy and authentication.
Tamara Kogan Smalltalk development, Cincom Systems > -----Original Message----- > From: [hidden email] > [mailto:[hidden email]] On Behalf Of Philippe Demaecker > Sent: Monday, March 21, 2011 12:22 PM > To: [hidden email] > Subject: [vwnc] HTTP Basic Authentication & SOAP > > Hello list, > > > > We are currently using a WSOpentTalk SOAP service to > integrate with one of our customer web services. > > > > The tests were going well, but in the meantime, an additional > requirement has popped up: the service should go through a > proxy using basic HTTP authentication instead of > communicating directly with the final WS endpoint. > > > > Is there support for this in VW 7.7? > > > > Any help appreciated. > > > > Kind Regards, > > Philippe > > _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Hello Tamara,
Thanks for the tip. I indeed read in the doc that authentication was supported using the WsdlClient. The whole interface has already been developed using the OT and I'm not sure how much work it will be to rewrite the integration using the WsdlClient approach. Can I just 'switch' clients? Instead of sending messages to the OT proxy I should just invoke WsdlClient >>executeSelector: ?. Are complex types handled to same way as in the OT approach? In general, when is the OT approach preferred over the WsdlClient? Kind regards, Philippe ________________________________________ From: Kogan, Tamara [[hidden email]] Sent: Monday, March 21, 2011 6:03 PM To: Philippe Demaecker; [hidden email] Subject: RE: [vwnc] HTTP Basic Authentication & SOAP To provide Http authentication you need to switch from Opentalk client to WsdlClient and use #transportClient (HttpClient) to set proxy and authentication. Tamara Kogan Smalltalk development, Cincom Systems > -----Original Message----- > From: [hidden email] > [mailto:[hidden email]] On Behalf Of Philippe Demaecker > Sent: Monday, March 21, 2011 12:22 PM > To: [hidden email] > Subject: [vwnc] HTTP Basic Authentication & SOAP > > Hello list, > > > > We are currently using a WSOpentTalk SOAP service to > integrate with one of our customer web services. > > > > The tests were going well, but in the meantime, an additional > requirement has popped up: the service should go through a > proxy using basic HTTP authentication instead of > communicating directly with the final WS endpoint. > > > > Is there support for this in VW 7.7? > > > > Any help appreciated. > > > > Kind Regards, > > Philippe > > vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Hi,
It seems OT uses Struct objects to represent complex objects, which means no compatibility with the my implementation, right? I read from the 7.7 docs: "Class WsdlClient supports all standard forms of HTTP authentication (e.g., Basic, Digest and NTLM schemas). Instances of WsdlClient use an HttpClient object as a transport mechanism, and the latter provides the actual support for authentication.HTTP authentication is presently available only for applications using the WsdlClient. This functionality is under active development for Opentalk and will be included in a future release." What is the status on this? Is there anything I can use yet? Thank you, Philippe -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Philippe Demaecker Sent: maandag 21 maart 2011 23:28 To: Kogan, Tamara; [hidden email] Subject: Re: [vwnc] HTTP Basic Authentication & SOAP Hello Tamara, Thanks for the tip. I indeed read in the doc that authentication was supported using the WsdlClient. The whole interface has already been developed using the OT and I'm not sure how much work it will be to rewrite the integration using the WsdlClient approach. Can I just 'switch' clients? Instead of sending messages to the OT proxy I should just invoke WsdlClient >>executeSelector: ?. Are complex types handled to same way as in the OT approach? In general, when is the OT approach preferred over the WsdlClient? Kind regards, Philippe ________________________________________ From: Kogan, Tamara [[hidden email]] Sent: Monday, March 21, 2011 6:03 PM To: Philippe Demaecker; [hidden email] Subject: RE: [vwnc] HTTP Basic Authentication & SOAP To provide Http authentication you need to switch from Opentalk client to WsdlClient and use #transportClient (HttpClient) to set proxy and authentication. Tamara Kogan Smalltalk development, Cincom Systems > -----Original Message----- > From: [hidden email] > [mailto:[hidden email]] On Behalf Of Philippe Demaecker > Sent: Monday, March 21, 2011 12:22 PM > To: [hidden email] > Subject: [vwnc] HTTP Basic Authentication & SOAP > > Hello list, > > > > We are currently using a WSOpentTalk SOAP service to integrate with > one of our customer web services. > > > > The tests were going well, but in the meantime, an additional > requirement has popped up: the service should go through a proxy using > basic HTTP authentication instead of communicating directly with the > final WS endpoint. > > > > Is there support for this in VW 7.7? > > > > Any help appreciated. > > > > Kind Regards, > > Philippe > > vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Hello,
We were able to figure it out with the help of a collegue. It seems the use of structs vs. real objects is configurable, so the switch to WsdlClient should be an easy one. Best, Philippe -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Philippe Demaecker Sent: dinsdag 22 maart 2011 9:50 To: Kogan, Tamara; [hidden email] Subject: Re: [vwnc] HTTP Basic Authentication & SOAP Hi, It seems OT uses Struct objects to represent complex objects, which means no compatibility with the my implementation, right? I read from the 7.7 docs: "Class WsdlClient supports all standard forms of HTTP authentication (e.g., Basic, Digest and NTLM schemas). Instances of WsdlClient use an HttpClient object as a transport mechanism, and the latter provides the actual support for authentication.HTTP authentication is presently available only for applications using the WsdlClient. This functionality is under active development for Opentalk and will be included in a future release." What is the status on this? Is there anything I can use yet? Thank you, Philippe -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Philippe Demaecker Sent: maandag 21 maart 2011 23:28 To: Kogan, Tamara; [hidden email] Subject: Re: [vwnc] HTTP Basic Authentication & SOAP Hello Tamara, Thanks for the tip. I indeed read in the doc that authentication was supported using the WsdlClient. The whole interface has already been developed using the OT and I'm not sure how much work it will be to rewrite the integration using the WsdlClient approach. Can I just 'switch' clients? Instead of sending messages to the OT proxy I should just invoke WsdlClient >>executeSelector: ?. Are complex types handled to same way as in the OT approach? In general, when is the OT approach preferred over the WsdlClient? Kind regards, Philippe ________________________________________ From: Kogan, Tamara [[hidden email]] Sent: Monday, March 21, 2011 6:03 PM To: Philippe Demaecker; [hidden email] Subject: RE: [vwnc] HTTP Basic Authentication & SOAP To provide Http authentication you need to switch from Opentalk client to WsdlClient and use #transportClient (HttpClient) to set proxy and authentication. Tamara Kogan Smalltalk development, Cincom Systems > -----Original Message----- > From: [hidden email] > [mailto:[hidden email]] On Behalf Of Philippe Demaecker > Sent: Monday, March 21, 2011 12:22 PM > To: [hidden email] > Subject: [vwnc] HTTP Basic Authentication & SOAP > > Hello list, > > > > We are currently using a WSOpentTalk SOAP service to integrate with > one of our customer web services. > > > > The tests were going well, but in the meantime, an additional > requirement has popped up: the service should go through a proxy using > basic HTTP authentication instead of communicating directly with the > final WS endpoint. > > > > Is there support for this in VW 7.7? > > > > Any help appreciated. > > > > Kind Regards, > > Philippe > > vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Hi Philippe,
I would even suggest to use WsdlClassBuilder to create subclasses from WsdlClient. In this case there is no difference in code for Opentalk client and WsdlClient subclass. As an example see WebServicesDemo TestCreateWSClients>>testWsdlSpecificClient To create subclasses from WsdlClient: classBuilder := WsdlClassBuilder readFrom: wsdlSchema readStream inNamespace: 'MyNamespace'. classBuilder package: 'MyPackage'. classBuilder createClientClasses. > available only for applications using the WsdlClient. This > functionality is under active development for Opentalk and > will be included in a future release." > > What is the status on this? Is there anything I can use yet? Last few releases we have worked on providing WSDL 2.0 and SOAP 1.2 support. Unfortunately it consumed all our time and we were not able to make any progress in adding authentication features to Opentalk framework. > Can I just 'switch' clients? Instead of sending messages to > the OT proxy I should just invoke WsdlClient > >>executeSelector: ?. Are complex types handled to same way > as in the OT approach? There is no difference in using complex type as Object or Structs for both clients. > In general, when is the OT approach preferred over the WsdlClient? As it is right now if an application has to use Http proxies or authentication there is no choice but WsdlClient. Tamara Kogan Smalltalk development, Cincom Systems > -----Original Message----- > From: Philippe Demaecker [mailto:[hidden email]] > Sent: Tuesday, March 22, 2011 7:26 AM > To: Philippe Demaecker; Kogan, Tamara; [hidden email] > Subject: RE: [vwnc] HTTP Basic Authentication & SOAP > > Hello, > > We were able to figure it out with the help of a collegue. It > seems the use of structs vs. real objects is configurable, so > the switch to WsdlClient should be an easy one. > > Best, > Philippe > > -----Original Message----- > From: [hidden email] > [mailto:[hidden email]] On Behalf Of Philippe Demaecker > Sent: dinsdag 22 maart 2011 9:50 > To: Kogan, Tamara; [hidden email] > Subject: Re: [vwnc] HTTP Basic Authentication & SOAP > > Hi, > > It seems OT uses Struct objects to represent complex objects, > which means no compatibility with the my implementation, right? > > I read from the 7.7 docs: > > "Class WsdlClient supports all standard forms of HTTP > authentication (e.g., Basic, Digest and NTLM schemas). > Instances of WsdlClient use an HttpClient object as a > transport mechanism, and the latter provides the actual > support for authentication.HTTP authentication is presently > available only for applications using the WsdlClient. This > functionality is under active development for Opentalk and > will be included in a future release." > > What is the status on this? Is there anything I can use yet? > > Thank you, > Philippe > > > -----Original Message----- > From: [hidden email] > [mailto:[hidden email]] On Behalf Of Philippe Demaecker > Sent: maandag 21 maart 2011 23:28 > To: Kogan, Tamara; [hidden email] > Subject: Re: [vwnc] HTTP Basic Authentication & SOAP > > Hello Tamara, > > Thanks for the tip. I indeed read in the doc that > authentication was supported using the WsdlClient. > > The whole interface has already been developed using the OT > and I'm not sure how much work it will be to rewrite the > integration using the WsdlClient approach. > > Can I just 'switch' clients? Instead of sending messages to > the OT proxy I should just invoke WsdlClient > >>executeSelector: ?. Are complex types handled to same way > as in the OT approach? > > In general, when is the OT approach preferred over the WsdlClient? > > Kind regards, > Philippe > ________________________________________ > From: Kogan, Tamara [[hidden email]] > Sent: Monday, March 21, 2011 6:03 PM > To: Philippe Demaecker; [hidden email] > Subject: RE: [vwnc] HTTP Basic Authentication & SOAP > > To provide Http authentication you need to switch from > Opentalk client to WsdlClient and use #transportClient > (HttpClient) to set proxy and authentication. > > > Tamara Kogan > Smalltalk development, > Cincom Systems > > > > -----Original Message----- > > From: [hidden email] > > [mailto:[hidden email]] On Behalf Of Philippe Demaecker > > Sent: Monday, March 21, 2011 12:22 PM > > To: [hidden email] > > Subject: [vwnc] HTTP Basic Authentication & SOAP > > > > Hello list, > > > > > > > > We are currently using a WSOpentTalk SOAP service to integrate with > > one of our customer web services. > > > > > > > > The tests were going well, but in the meantime, an additional > > requirement has popped up: the service should go through a > proxy using > > basic HTTP authentication instead of communicating directly > with the > > final WS endpoint. > > > > > > > > Is there support for this in VW 7.7? > > > > > > > > Any help appreciated. > > > > > > > > Kind Regards, > > > > Philippe > > > > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Hey Tamara,
Thanks for the info. On my test server, authentication is working perfectly using the suggestions you made. Best, Philippe -----Original Message----- From: Kogan, Tamara [mailto:[hidden email]] Sent: dinsdag 22 maart 2011 14:36 To: Philippe Demaecker; [hidden email] Subject: RE: [vwnc] HTTP Basic Authentication & SOAP Hi Philippe, I would even suggest to use WsdlClassBuilder to create subclasses from WsdlClient. In this case there is no difference in code for Opentalk client and WsdlClient subclass. As an example see WebServicesDemo TestCreateWSClients>>testWsdlSpecificClient To create subclasses from WsdlClient: classBuilder := WsdlClassBuilder readFrom: wsdlSchema readStream inNamespace: 'MyNamespace'. classBuilder package: 'MyPackage'. classBuilder createClientClasses. > available only for applications using the WsdlClient. This > functionality is under active development for Opentalk and will be > included in a future release." > > What is the status on this? Is there anything I can use yet? Last few releases we have worked on providing WSDL 2.0 and SOAP 1.2 support. Unfortunately it consumed all our time and we were not able to make any progress in adding authentication features to Opentalk framework. > Can I just 'switch' clients? Instead of sending messages to the OT > proxy I should just invoke WsdlClient > >>executeSelector: ?. Are complex types handled to same way > as in the OT approach? There is no difference in using complex type as Object or Structs for both clients. > In general, when is the OT approach preferred over the WsdlClient? As it is right now if an application has to use Http proxies or authentication there is no choice but WsdlClient. Tamara Kogan Smalltalk development, Cincom Systems > -----Original Message----- > From: Philippe Demaecker [mailto:[hidden email]] > Sent: Tuesday, March 22, 2011 7:26 AM > To: Philippe Demaecker; Kogan, Tamara; [hidden email] > Subject: RE: [vwnc] HTTP Basic Authentication & SOAP > > Hello, > > We were able to figure it out with the help of a collegue. It > seems the use of structs vs. real objects is configurable, so > the switch to WsdlClient should be an easy one. > > Best, > Philippe > > -----Original Message----- > From: [hidden email] > [mailto:[hidden email]] On Behalf Of Philippe Demaecker > Sent: dinsdag 22 maart 2011 9:50 > To: Kogan, Tamara; [hidden email] > Subject: Re: [vwnc] HTTP Basic Authentication & SOAP > > Hi, > > It seems OT uses Struct objects to represent complex objects, > which means no compatibility with the my implementation, right? > > I read from the 7.7 docs: > > "Class WsdlClient supports all standard forms of HTTP > authentication (e.g., Basic, Digest and NTLM schemas). > Instances of WsdlClient use an HttpClient object as a > transport mechanism, and the latter provides the actual > support for authentication.HTTP authentication is presently > available only for applications using the WsdlClient. This > functionality is under active development for Opentalk and > will be included in a future release." > > What is the status on this? Is there anything I can use yet? > > Thank you, > Philippe > > > -----Original Message----- > From: [hidden email] > [mailto:[hidden email]] On Behalf Of Philippe Demaecker > Sent: maandag 21 maart 2011 23:28 > To: Kogan, Tamara; [hidden email] > Subject: Re: [vwnc] HTTP Basic Authentication & SOAP > > Hello Tamara, > > Thanks for the tip. I indeed read in the doc that > authentication was supported using the WsdlClient. > > The whole interface has already been developed using the OT > and I'm not sure how much work it will be to rewrite the > integration using the WsdlClient approach. > > Can I just 'switch' clients? Instead of sending messages to > the OT proxy I should just invoke WsdlClient > >>executeSelector: ?. Are complex types handled to same way > as in the OT approach? > > In general, when is the OT approach preferred over the WsdlClient? > > Kind regards, > Philippe > ________________________________________ > From: Kogan, Tamara [[hidden email]] > Sent: Monday, March 21, 2011 6:03 PM > To: Philippe Demaecker; [hidden email] > Subject: RE: [vwnc] HTTP Basic Authentication & SOAP > > To provide Http authentication you need to switch from > Opentalk client to WsdlClient and use #transportClient > (HttpClient) to set proxy and authentication. > > > Tamara Kogan > Smalltalk development, > Cincom Systems > > > > -----Original Message----- > > From: [hidden email] > > [mailto:[hidden email]] On Behalf Of Philippe Demaecker > > Sent: Monday, March 21, 2011 12:22 PM > > To: [hidden email] > > Subject: [vwnc] HTTP Basic Authentication & SOAP > > > > Hello list, > > > > > > > > We are currently using a WSOpentTalk SOAP service to integrate with > > one of our customer web services. > > > > > > > > The tests were going well, but in the meantime, an additional > > requirement has popped up: the service should go through a > proxy using > > basic HTTP authentication instead of communicating directly > with the > > final WS endpoint. > > > > > > > > Is there support for this in VW 7.7? > > > > > > > > Any help appreciated. > > > > > > > > Kind Regards, > > > > Philippe > > > > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Free forum by Nabble | Edit this page |