Sven Dens » Flash http://www.svendens.com deserialize me Tue, 22 Sep 2009 09:32:48 +0000 http://wordpress.org/?v=2.8.6 en hourly 1 SOAP headers in Flex and WS-Security http://www.svendens.com/flex/soap-headers-in-flex-and-ws-security/ http://www.svendens.com/flex/soap-headers-in-flex-and-ws-security/#comments Thu, 21 Feb 2008 15:00:04 +0000 Sven Dens http://www.svendens.be/blog/archives/27 UPDATE (06-16-2009): The problem with generating a correct nonce has been fixed!
It turned out to be a problem in the WSSEUsernameToken class in the com.adobe.crypto package in as3corelib.
A VERY big thank you goes to Tom from FlexibleFactory for pointing me to the solution and to Koen Weyn for fixing the bugs!

Dear readers,

I just spent 2 entire days trying to figure out how to consume a SOAP Webservice that requires a SOAP-header and WS-Security in Flex. Hopefully this post will help you out if you’re looking to do the same thing.

Download demo files here.

Let me start off by saying that the Import Web Service (WSDL) wizard in Flex 3 doesn’t work as it should!
The generated classes return invalid XML to the SOAP-request, and adding headers to your request is completely neglected.
But I did get it to work using the classical <mx:Webservice> tag and some hand-coding.

Here’s how to do it:

First you need a copy of the as3corelib (only if you need the WS-Security), more specifically you need the com.adobe.crypto.WSSEUsernameToken.as class.
This class returns a token as a String, which I think is not very convenient, so I added another function called “getUsernameTokenAsArray” which returns the different token elements required for WS-Security in an Array. This way you can just “pluck” the parts you need without having to parse a String.

Next you need to write some AS3 classes to map the datatypes expected by the WebService to your Flex app, and vice-versa.

I wrote a little utility class that lets you easily insert different types of SOAP-headers to your requests.
Currently methods are implemented for returning headers containing WS-Security. Feel free to use it and add your own methods for additional SOAP-header-types to it.
Here it is:

package be.svendens.util
{
    import mx.rpc.soap.SOAPHeader;
    import com.adobe.crypto.WSSEUsernameToken;

    public class SOAPHeaderUtil
    {
        private static const WSSE_SECURITY:QName = new QName( "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd", "Security" );
   
        public static function returnWSSEHeaderWithNonceAndTimestamp(username:String, password:String, nonce:String=null, timestamp:Date=null):SOAPHeader
        {
            var userToken:String    = "UsernameToken-"+Math.round(Math.random()*999999).toString();
            var wsseToken:Array     = WSSEUsernameToken.getUsernameTokenAsArray(username, password, nonce, timestamp);
            var headerXML:XML       = <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
                                        <wsse:UsernameToken wsu:Id={userToken} xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd'>
                                            <wsse:Username>{wsseToken[0]}</wsse:Username>
                                            <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest">{wsseToken[1]}</wsse:Password>
                                            <wsse:Nonce>{wsseToken[2]}</wsse:Nonce>
                                            <wsu:Created>{wsseToken[3]}</wsu:Created>
                                        </wsse:UsernameToken>
                                    </wsse:Security>
           
            var header:SOAPHeader   = new SOAPHeader( WSSE_SECURITY, headerXML );
            return header;
        }
       
        public static function returnWSSEHeaderWithoutNonceAndTimestamp(username:String, password:String):SOAPHeader
        {
            var userToken:String    = "UsernameToken-"+Math.round(Math.random()*999999).toString();
            var wsseToken:Array     = WSSEUsernameToken.getUsernameTokenAsArray(username, password);
            var headerXML:XML       = <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
                                        <wsse:UsernameToken wsu:Id={userToken} xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd'>
                                            <wsse:Username>{wsseToken[0]}</wsse:Username>
                                            <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest">{wsseToken[1]}</wsse:Password>
                                        </wsse:UsernameToken>
                                    </wsse:Security>
           
            var header:SOAPHeader   = new SOAPHeader( WSSE_SECURITY, headerXML );
            return header;
        }
    }
}

Now you can call your webservice and add headers like this:

var header:SOAPHeader = SOAPHeaderUtil.returnWSSEHeaderWithNonceAndTimestamp("username", "password");
myService.addHeader(header);

Basically you create an <mx:Webservice>, pass it the correct parameters for your webservice. Then create a function to add the headers.
Call the clearHeaders method of your webservice (it’s a default method for a webservice object) to clear any existing headers, next call the addHeader method to attach the new header.

Finally call your webservice operation with the necessary input parameters and there you go: a nice SOAP-envelope with headers and WS-Security!

You can download a complete demo containing all necessary classes and a sample MXML file here.

WSDL loaded
Invoking SOAP operation CreateCTAScheduleItem
Encoding SOAP request envelope
Encoding SOAP request body
'B5C37908-53AE-B85B-EDE1-3C3A54EB5255' producer sending message 'F9F59B36-51D7-DCC7-C673-3C3A59283DE9'
'direct_http_channel' channel sending message:
(mx.messaging.messages::SOAPMessage)#0
body = "
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <SOAP-ENV:Header>
        <wsse:Security SOAP-ENV:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
            <wsse:UsernameToken wsu:Id="UsernameToken-502651" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
                <wsse:Username>Flex</wsse:Username>
                <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest">mA5XaNPovDGiotMyb/e8A2fiIbU=</wsse:Password>
                <wsse:Nonce>MDU3NDc4OTIzODE2MjMzODc=</wsse:Nonce>
                <wsu:Created>2008-02-21T14:41:39.251Z</wsu:Created>
            </wsse:UsernameToken>
        </wsse:Security>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
        <schema:CreateCTAScheduleItemRequest xmlns:schema="http://yournamespace">
            <timePeriod>
                <StartDate>2008-02-21T13:41:38.654Z</StartDate>
                <EndDate>2008-02-21T13:41:38.654Z</EndDate>
            </timePeriod>
            <priority>4</priority>
            <cta>test</cta>
            <applicationURL>http://blog.svendens.be</applicationURL>
            <repeatInterval>2</repeatInterval>
        </schema:CreateCTAScheduleItemRequest>
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>"

I’m still struggling with the authentication however.
The SOAP-request looks exactly as it should and validates fine by the WSDL, but when using the Nonce and Created elements my username/digest and nonce keep getting rejected by the server. Without the nonce everything works like a charm.
Any of you guru’s out there know how to tackle this last problem?

]]> http://www.svendens.com/flex/soap-headers-in-flex-and-ws-security/feed/ 28 Email and cell phone validation in AS2 and AS3 http://www.svendens.com/actionscript/email-and-cell-phone-validation-in-as2-and-as3/ http://www.svendens.com/actionscript/email-and-cell-phone-validation-in-as2-and-as3/#comments Tue, 22 May 2007 14:04:25 +0000 Sven Dens http://www.svendens.be/blog/archives/9 I just wrote 2 simple classes to validate email addresses and Belgian cell phone numbers in AS2 and AS3.
Might come in handy for you, they’re available for download here.

I included FLA’s for Flash8 and FlashCS3 for AS2 and AS3.
They show 2 TextInput components, one for an email address and one for a cell phone number.
The cell phone validation includes a “strip” function. Since people tend to enter their phone numbers in different ways, dots, blanks and slashes are removed from the input before validating the number.

AS2 Usage example:

import be.boulevart.as2.validation.Email;
import be.boulevart.as2.validation.GSM;

class be.boulevart.as2.playfield.Validation extends MovieClip
{
    // Elements on Stage
    private var check_btn:Button;
    private var email_ti, phone_ti:TextInput;
    private var emailOk:Boolean;
    private var gsmOk:Boolean;

    public function Validation() {}

    private function onLoad():Void
    {
        check_btn.addEventListener("click", Delegate.create(this, doValidation));
        email_ti.tabIndex   = 1;
        phone_ti.tabIndex   = 2;
        check_btn.tabIndex  = 3;
    }

    private function doValidation():Void
    {
        emailOk = Email.validate(email_ti.text);
        gsmOk = GSM.validate(phone_ti.text);

        if(!emailOk)
        {
            Alert.show("Invalid email address!", "Error", Alert.OK, this);
        } else {
            Alert.show("Email address is valid!", "You rock dude", Alert.OK, this);
        }

        if (!gsmOk)
        {
            Alert.show("Invalid cell phone number!", "Error", Alert.OK, this);
        }
        else
        {
            Alert.show("Cell phone number is valid!", "You rock dude", Alert.OK, this);
        }
    }
}

AS3 Usage example:

package be.boulevart.as3.playfield
{
    import be.boulevart.as3.validation.Email;
    import be.boulevart.as3.validation.GSM;
    import flash.display.MovieClip;
    import flash.events.*;

    public class Validation extends MovieClip
    {
        protected var emailOk:Boolean;
        protected var gsmOk:Boolean;

        public function Validation()
        {
            check_btn.addEventListener("click", doValidation);
            email_ti.tabIndex = 1;
            phone_ti.tabIndex = 2;
            check_btn.tabIndex = 3;
        }

        private function doValidation(evt:Event):void
        {
            emailOk = Email.validate(email_ti.text);
            gsmOk = GSM.validate(phone_ti.text);

            if(!emailOk)
            {
                trace("Invalid email address!");
                email_result.text = "Invalid email!";
            }
            else
            {
                trace("Email address is valid!");
                email_result.text = "Valid email!";
            }

            if (!gsmOk)
            {
                trace("Invalid cell phone number!");
                phone_result.text = "Invalid phone!";
            }
            else
            {
                trace("Cell phone number is valid!");
                phone_result.text = "Valid phone!";
            }
        }
    }
}

Enjoy! :-)

]]> http://www.svendens.com/actionscript/email-and-cell-phone-validation-in-as2-and-as3/feed/ 6