Direct invoke and url user/password challenge/response

hi andreas,

You can send HTTP  authentication credential headers in directinvoke when invoking an authenticated site.

Step 1)
Define a reusable global macro to format & encode HTTP basic auth credentials.
Add the following EMML macro snippet to <tomcat>/webapps/presto/WEB-INF/classes/global.emml-macros

   <macro name="computeBasicAuth">
       <input name="user" type="string"/>
       <input name="password" type="string"/>
       <output name="basicauth" type="string"/>
       <presto-meta name="macrotype">system</presto-meta>

       <script type="text/javascript" >
               <![CDATA[
               var userPassword =  new Packages.java.lang.String(user
+ ":" + password);
               basicauth = "Basic " +
                           Packages.sun.misc.BASE64Encoder().encode
(userPassword.getBytes());
               ]]>
       </script>

   </macro>

Step 2)
Use this Macro to compute basic-auth headers, and subsequently send those HTTP headers in <directinvoke/> call.

     <input name="user" type="string" default="xyz"/>
       <input name="password" type="string" default="xyzxyz"/>

       <output name="result" type="string"/>

       <variables>
           <input name="basicauth" type="string" />
           <variable name="reqheaders" type="document"/>
           <variable name="payload" type="document">
               <stubrequest/>
           </variable>
       </variables>

       <macro:computeBasicAuth user="$user" password="$password"
outputvariable="$basicauth"/>

       <!-- Build Basic Auth Header -->
       <constructor outputvariable="reqheaders">
               <![CDATA[
               <headers>
                    <Authorization>{$basicauth}</Authorization>
               </headers>
               ]]>
       </constructor>

       <directinvoke endpoint="http://serviceEndpoint"
                       method="post"
                       header="$reqheaders"
                       requestbody="$payload"
                       outputvariable="result"/>

Let us know if you have further clarification / issues.

Raj,

Thank you for the code snippet. I see this as a post request to authenticate and then getting back a cookie that I can use in the header for subsquent authenticated calls against the target system. Is this a correct assumption?

Bill

Hi Bill,

Yes, you can use cookies to propagate authentication state.  There is a cookie attribute in <directinvoke/> to receive & send cookies i.e.,

            <directinvoke endpoint="$redirecturl" cookies="$cookies" outputvariable="result"/>
You can check out mashupclient/samples/igoogle.emml   EMML sample for a demonstration of cookie for propagating authentication token.

Raj,

Thank you, I did not know that was in the igoogle sample, makes sense now that you have mentioned it. I'll take a look at it.

We use an RSA Cleatrust SSO solution, as RSA is one of our organizations, should work with that implementation

Great stuff,

Still Love the Glasses,

Bill