In the safety critical and high data quality domains, such as aviation – secure web services with digitally signed and reliable messages are essential to maintaining the provenance and quality of data, helping aeronautical web service customers remain compliant with ICAO legislation. Here at Snowflake we have been quietly creating and deploying secured and encrypted Location Based Services for years – but haven’t really let the internet hear about it… yet.

So here goes…..

For the last few years, before I joined the team here, Snowflake has been working with SOAP web service implementations exchanging GML through a managed BPEL workflow with the Ordnance Survey and other National Mapping Agencies for their geospatial production systems. More recently, in the aviation domain, the Snowflake Labs team has been looking into the performance of SOAP based Web Feature Service (WFS) implementations where Aeronautical Information, encoded as AIXM, could be compressed, encrypted and digitally signed.

A key element to developing support for some of the advanced WS-Security standards was not to develop them ourselves, but to integrate with the Java Spring Framework – the Snowflake deployable WFS product has implemented the “hooks” or API access points to integrate with the Spring Java Framework, enabling the use of Java application server configuration for security (JBOSS, MULE etc) – where the application server supports the Spring Framework.

The Spring security framework documentation is here:

The Snowflake WFS configuration tools support transport level security and payload  security (digital signatures and encryption), and the actual handling of tokens and authentication is all integrated to the hosting application server via Spring (e.g. JBOSS).
In this way the team has implemented and integrated support for WS-Security and WS-ReliableMessaging. In terms of authorisation and authentication, the team has secured the Snowflake WFS using a variety of mechanisms, including a short trial with the GeoXACML Policy engine/decision point extension to XACML, as well as using Kerberos (authentication) and LDAP (authorisation).

For those who can parse complex XML with their eyes – an example SOAP response containing some GML with signature and encryption is shown below:

<?xml version="1.0" encoding="UTF-8"?>
<!--Created by null 1.45 Build 23659 from 2011-06-15 11:37-->
<!--Snowflake Software Ltd. (>
<!--Data Copyright: none

The data is provided on an "as seen / as is" basis, and is intended for demonstration purposes only.  Snowflake Software provides no express or limited warranty of any kind, including but not limited to those of merchantability, fitness for a particular purpose and accepts no liability whatsoever for or in connection with the use of the data.-->
<soap:Envelope xmlns:soap="" xmlns:aixm="" xmlns:gco="" xmlns:gmd="" xmlns:gml="" xmlns:gsr="" xmlns:gss="" xmlns:gts="" xmlns:message="" xmlns:xlink="" xmlns:xs="" xmlns:xsi="">
		<wsse:Security xmlns:wsse="" xmlns:wsu="" soap:mustUnderstand="1">
			<wsse:UsernameToken xmlns:wsse11="" wsu:Id="UsernameToken-4205">
			<wsc:DerivedKeyToken xmlns:wsc="" wsu:Id="DK-4206">
					<wsse:Reference URI="#UsernameToken-4205" ValueType=""/>
			<xenc:ReferenceList xmlns:xenc="">
				<xenc:DataReference URI="#ED-4207"/>
			<wsse:UsernameToken xmlns:wsse11="" wsu:Id="UsernameToken-4201">
			<wsc:DerivedKeyToken xmlns:wsc="" wsu:Id="DK-4202">
					<wsse:Reference URI="#UsernameToken-4201" ValueType=""/>
			<ds:Signature xmlns:ds="" Id="SIG-4204">
					<ds:CanonicalizationMethod Algorithm="">
						<ec:InclusiveNamespaces xmlns:ec="" PrefixList="aixm gco gmd gml gsr gss gts message soap xlink xs xsi"/>
					<ds:SignatureMethod Algorithm=""/>
					<ds:Reference URI="#id-4203">
							<ds:Transform Algorithm="">
								<ec:InclusiveNamespaces xmlns:ec="" PrefixList="aixm gco gmd gml gsr gss gts message xlink xs xsi"/>
						<ds:DigestMethod Algorithm=""/>
				<ds:KeyInfo Id="KI-6710B5B59685A9940C13086675488011201">
					<wsse:SecurityTokenReference wsu:Id="STR-6710B5B59685A9940C13086675488011202">
						<wsse:Reference URI="#DK-4202"/>
	<soap:Body xmlns:wsu="" wsu:Id="id-4203">
		<xenc:EncryptedData xmlns:xenc="" Id="ED-4207" Type="">
			<xenc:EncryptionMethod Algorithm=""/>
			<ds:KeyInfo xmlns:ds="">
				<wsse:SecurityTokenReference xmlns:wsse="">
					<wsse:Reference URI="#DK-4206"/>


Chartered Engineer with the IET and Principal Consultant with Snowflake Software Ltd, Alexis James Brooker is based in the UK, with extensive experience of technical project delivery, business development and consulting in the software and open standard web services domain. Alex’s current business development role spans the Defence and Maritime sectors of Snowflake’s business.

You can follow Alex on twitter @alexisbrooker or search for him on LinkedIn and G+

By | 2012-08-16T12:48:37+00:00 August 16th, 2012|Air Traffic Management, News, Snowflake Labs, Web Services|