Does Microsoft have plans to implement WSE for CF ?

  • Thread starter Thread starter Tim Bartle
  • Start date Start date
T

Tim Bartle

I am currently working on a large project requiring secure web-services over
wireless connections from Pocket PCs. Has Microsoft announced any plans to
make Web Service Enhancements available for CF ? I am mainly interested in
the enhancements which are available in WSE 1.0.

I have seen an article claiming relative success using the standard WSE for
..NET with a pre-release version of CF but we can only realistically use
supported solutions for this project.

Any ideas ? Rumors etc.... We don't go live for nearly a year so we have a
little leeway.

Tim Bartle
Principal Technical Consultant
Intraweb Software
 
Tim,

We are actively investigating support for WSE 2.0 on the Compact Framework.
I would be very interested in finding out more details on your customer
requirements for WSE and specifically, what features in WSE do you think
are the most critical.

Bruce Johnson
.NET Compact Framework

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Here is my 2nd cut at WSE for .NETcf ...
http://www.gotdotnet.com/community/usersamples/Default.aspx?query=spwse
(read 'default.htm' in the 'spWse' directory)
It does WS-Utility Timestamp, WS-Addressing / WS-Routing, DIME,
and WS-Security (including Authentication, Xml-Encryption, and
Xml-Signature).
My WS test harness is some of the WSE 2.0 samples.
[it should be posted to devbuzz.com anyday now?]

We need System.Web.Services beefed up a bit (see the bugs in my article).
Timestamp and Addressing are easy.
DIME is easy, and makes perfect sense for devices (i.e. tell the MapPoint
..NET team).
WS-Security is the building block for the security stack so that makes sense
too.
Of course we'll need System.Security.Cryptography for that.
(http://www.devbuzz.com/content/zinc_smartphone_cryptography_pg1.asp)
The X509Certificate needs some work too.
The Sys.Sec.Crytpo.X509Cert should accept a CERT_CONTEXT IntPtr,
and the Ms.Web.Services.X509 extensions for KeyId and private key would help
too,
so we would not have to pInvoke the Certificate API
(really difficult with nested structures and such).
[basically, the above is what WSE 1.0 supported]

WSE 2.0 also does WS-Policy, Kerberos, and WS-SecureConversation,
but we can probably wait on those.
The Ms.Web.Services.Messaging model might be useful,
because it might be an easy way to host Web Services from devices,
without having ASP.NET.
Filters are pretty simple, so that should be easy to hook.
The app.config stuff would be nice, but we could decorate the proxies
instead.

Thanks,
casey

Bruce Johnson said:
Tim,

We are actively investigating support for WSE 2.0 on the Compact Framework.
I would be very interested in finding out more details on your customer
requirements for WSE and specifically, what features in WSE do you think
are the most critical.

Bruce Johnson
NET Compact Framework

This posting is provided "AS IS" with no warranties, and confers no
Click to expand...
rights.
 
oh yeah ...
WS-ReliableMessaging would make perfect sense too.
once its available.

casey chesnut said:
Here is my 2nd cut at WSE for .NETcf ...
http://www.gotdotnet.com/community/usersamples/Default.aspx?query=spwse
(read 'default.htm' in the 'spWse' directory)
It does WS-Utility Timestamp, WS-Addressing / WS-Routing, DIME,
and WS-Security (including Authentication, Xml-Encryption, and
Xml-Signature).
My WS test harness is some of the WSE 2.0 samples.
[it should be posted to devbuzz.com anyday now?]

We need System.Web.Services beefed up a bit (see the bugs in my article).
Timestamp and Addressing are easy.
DIME is easy, and makes perfect sense for devices (i.e. tell the MapPoint
.NET team).
WS-Security is the building block for the security stack so that makes sense
too.
Of course we'll need System.Security.Cryptography for that.
(http://www.devbuzz.com/content/zinc_smartphone_cryptography_pg1.asp)
The X509Certificate needs some work too.
The Sys.Sec.Crytpo.X509Cert should accept a CERT_CONTEXT IntPtr,
and the Ms.Web.Services.X509 extensions for KeyId and private key would help
too,
so we would not have to pInvoke the Certificate API
(really difficult with nested structures and such).
[basically, the above is what WSE 1.0 supported]

WSE 2.0 also does WS-Policy, Kerberos, and WS-SecureConversation,
but we can probably wait on those.
The Ms.Web.Services.Messaging model might be useful,
because it might be an easy way to host Web Services from devices,
without having ASP.NET.
Filters are pretty simple, so that should be easy to hook.
The app.config stuff would be nice, but we could decorate the proxies
instead.

Thanks,
casey

Bruce Johnson said:
Tim,

We are actively investigating support for WSE 2.0 on the Compact Framework.
I would be very interested in finding out more details on your customer
requirements for WSE and specifically, what features in WSE do you think
are the most critical.

Bruce Johnson
NET Compact Framework

This posting is provided "AS IS" with no warranties, and confers no
Click to expand...
rights.
Click to expand...
 
Hi Bruce,

We are doing a project for an organisation with strict security guidelines
for the operation of their computing devices. Our main priority therefore is
WS-Security and its surrounding plumbing. As we will be doing web-service
calls over GPRS and possibly blue-tooth, we could also do with
WS-ReliableMessaging, but that is a much lower priority for us.

Tim.
 
Back
Top