Web Service Authentication problem

Hi
I have created a portal service and exposed this service as a webservice. I am consuming this webservice in webdynpro.  Portal service contains 2 simple methods putdata() and getdatat().
When i access the webservice i am getting the following error.
"javax.xml.rpc.soap.SOAPFaultException: The User Authentification is not correct to access to the Portal Service com.sap.portal.prt.soap.GlobalData or the service was not found"
My Enterprise portal server is configured for SSO to back end R/3 system. I have checked for portal service availability and it is fine.
My Webdynpro and Portal are running on different machines. EP is running on AIX with SP11.
Any help please
Regards
NagaKishore V

Hi NagaKishore,
There had been no activity on this thread.Did you find the solution to your problem? Even I am getting the same exception while trying to access the webservice I created.

Similar Messages

  • XI Web Service Authentication problem

    Hi,
    I have a XI Web Service that our third-party PeopleSoft client is trying to consume. I tested the Web Service and that works. I used SOAP client testing tool that I have which posts SOAp message to the web service URL. Before i use this tool using Internext Explorer, I attempt to connect to the Web Service URL (by putting the entire web service URL in the Address Bar), it prompts me for the user name & password and upon successful authentication, MessageServlet gives me a success message.Once authenticated, i am successfully able to post SOAP messages to the Web Service URL.
    I provided my PeopleSoft team with the WSDL document, they uploaded into their system, made some configs, and the SOAP message that they are generating is as below
    As you can see in the SOAp message, they are attempting to pass the user name and password in SOAP header and I understand XI ignores SOAP headers OR that is at least not the way to authenticate.
    Shouldn't they be able to somehow authenticate themselves against SOAP adapter using User name and password that we provided them with and the send SOAP messages?
    ********<soap:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soap:Header>
    <wsse:Security soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
    <wsse:UsernameToken><wsse:Username>user name</wsse:Username><wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">password</wsse:Password></wsse:UsernameToken></wsse:Security></soap:Header><soap:Body><MI_EMP_ADDR_CHG_OSSERVICE xmlns="https://pics.sco.ca.gov"><PERSON_ID>BB000001</PERSON_ID><START_DATE>20100501</START_DATE><ADDR_LINE1>100 MAIN ST</ADDR_LINE1><ADDR_LINE2/><CITY>CORONA</CITY><COUNTY>RIVERSIDE</COUNTY><STATE>CA</STATE><ZIP_CODE>91881</ZIP_CODE></MI_EMP_ADDR_CHG_OSSERVICE></soap:Body></soap:Envelope>
    I will appreciate any ideas.
    Thanks,
    Saurabh

    Indeed, they should take care of the authentication according to supported XI mechanisms, as explained here :
    http://help.sap.com/saphelp_nw04/helpdata/en/1f/7e2441509fa831e10000000a1550b0/content.htm
    There is also a note #891877 that explains security level settings for SOAP adapter
    Chris

  • SOAP Web Service Authentication configuration

    Hello,
    I've got a little problem with Web Service authentication configuration.
    I'm working on the SAP NetWeaver CE EHP1 7.11. I also have a XMII application deployed on the server and there are some SOAP Web Services(over XMII Transactions) that require basic authentication.
    I use all Web Services in the EJB layer. So, I've generated proxy using SAP NetWeaver as a Web Service Runtime for generation. And Iuse an injection mechanism to get a service implementation:
    @WebServiceRef(name="GetBatchListService")
    private XacuteWS batchListWS;
    In this case I could use Single Service Administration application in the NetWeaver Administrator@SOA Management@Application and Scenario Communication to configure basic authentication for EVERY Web Service. And this configuration disappears after every redeploy.
    The question is how and where could I configure authentication for all web services?
    I've read a lot of documentation, but, unfortunately, I haven't found needed one. I could see 2 direction of searching now, it might help:
    1) Destination: Configure HTTP Destination or Web Service Template Destination and use it in all Web Services proxies somehow.
    2) Find Configuration way: Create a configuration group or anything else to configure all services from one screen.
    Best Regards,
    Dmitry

    Dimtris,
    If your WSDL url is pointing to the URL of the Adapter Engine as shownin the Hot to Use the SOAP adapter there is no option. You cannot add it to the SOAP Url.
    But, if you change the SOAP Url to the Url shown in this blog by Stefan Grube then you can add the user id and pasword to the url by adding sap- user=userid and sap-password = password.
    The optin shown ion the blog by Grube can be used as long as you do not have to use SOAP attachments and in this  case you would not need both sender SOAP adapter and a sender agreement.
    /people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
    Regards
    Bhavesh
    Regards
    Bhavesh

  • X.509 Web Service Authentication for ABAP AS Web Service Interaction

    We are trying to use X.509 web service authentication with SAP Web AS ABAP between 2 different SAP installations. Company 1 is trying to consume a web service set up by Company 2.
    Company 1 has installed Company 2's public key, generated the client proxy using Company 2's WSDL and created a corresponding lpconfig entry.
    Then company 2 has set up the profile parameter ICM/HTTPS/verify_client to accept certificates and imported Company 1's SLL client certificate and mapped the user in USREXTID.  Note that Company 1 uses self-signed certificates, so it does not have a root certificate, which is what the documentation says should be imported into the PSE instead of the SSL client certificate.
    When Company 1 tries the web service call, it receives a request to authenticate the web service from Company 2. (basic authentication logon screen, even though the web service configuration is set to X.509 Client Certificate.
    Should this work or is there a problem because Company 1 uses self-signed certificates or is there something else we are missing?

    >
    Connie Begovich wrote:
    > We are trying to use X.509 web service authentication with SAP Web AS ABAP between 2 different SAP installations. Company 1 is trying to consume a web service set up by Company 2.
    >
    > Company 1 has installed Company 2's public key, generated the client proxy using Company 2's WSDL and created a corresponding lpconfig entry.
    >
    > Then company 2 has set up the profile parameter ICM/HTTPS/verify_client to accept certificates and imported Company 1's SLL client certificate and mapped the user in USREXTID.  Note that Company 1 uses self-signed certificates, so it does not have a root certificate, which is what the documentation says should be imported into the PSE instead of the SSL client certificate.
    >
    > When Company 1 tries the web service call, it receives a request to authenticate the web service from Company 2. (basic authentication logon screen, even though the web service configuration is set to X.509 Client Certificate.
    >
    > Should this work or is there a problem because Company 1 uses self-signed certificates or is there something else we are missing?
    I think that the problem is in Service Authentication (in transaction sicf). You have to consume web-service, transmitting user-password for access.

  • Web service invocation problem on host hostname and port 8000 protocol : http logical port name : LP_WS_SMDAGENT_MONITORING

    hello colleagues,
    In the phase Connect Diagnostics dont show the Agent available in SLD, but when go to SLD i have the agents,
    Error,
    Connect Diagnostics Agent
    The table does not contain any data
    Agent availables in all SLD
    SOAP:1.007 SRT: Unupported xstream found: ("HTTP Code 401 : Unauthorized")
    Web service invocation problem on host hostname and port 8000 protocol : http logical port name : LP_WS_SMDAGENT_MONITORING
    Thanks

    OK, then pls follow below steps;
    - Go to step 'Create Users' in solman_setup System Preparation scenario and make sure the user SM_INTERN_WS has a green status. Use the 'Test Login' button to make sure the user is not locked and has correct credentials maintained in solman_setup
    - Immediately after checking the user status, navigate to Configure Connectivity->Enable Web Services and execute again the 'Create Logical Ports' automatic activity, in order to propagate the correct credentials to the Logical Port definitions.
    - If the above operation is not successful, repeat the two steps above, providing a different user Id in 'Create Users' step, eg SM_INTERN_W1. This will prevent situations where the user gets locked by Logical Ports using an obsolete password.
    Let me know the results.
    Regards,
    Vivek

  • PL SQL Web Service Authentication through LDAP

    I have created one PL SQL Web Service and I would like to provide token security through LDAP.
    I have configured LDAP for deployed webservice in oracle IAS 10.1.3 Service.
    Problem Description: <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="http://dbconnection1/MobileWebService.wsdl/types/"><env:Body><env:Fault><faultcode>env:MustUnderstand</faultcode><faultstring>SOAP must understand error: {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security</faultstring></env:Fault></env:Body></env:Envelope>
    I have provided LDAP authentication through oracle iAS Setup.
    Please help

    Hi I am looking out for a good friend of mine, Rajeev Dave from Vijaywada, if your the one, please email me [email protected]
    thanks,

  • Web Service authentication by security role

    I define an web service with authentication by security role.
    I access web service via web dynpro model in EP7.
    It appear below error:
    <b>Exception on execution of web service with WSDL URL 'http://XXX:50000/XXX/Config1?wsdl ' with operation 'XXXXXXXX' in interface 'XXXVi_Document'</b>
    how should i do to solve this problem ?

    Hi WU,
                Use this code with ur webservice & check the error in log file.May be we will get some more info abt this.
    This code will be in execute method
    Request_XXX reqData = new Request_XXXdbModel);
    reqData.wdSetInvocationLogEnabled(true);
    in the catch block give this
    logger.traceThrowableT(
         Severity.ERROR,
         wdComponentAPI.getApplication().getDeployableObjectPart().getName(),
         ex);
         //if (logger.beDebug()) {
         logger.fatalT(requestModel.wdGetRequestLog());
         logger.fatalT(requestModel.wdGetResponseLog());
         logger.fatalT(requestModel.associatedModelClassInfo().getModelInfo().toString());
         logger.fatalT(requestModel.toString());
    request model is ue model & ex is the exception in catch block.
    execute the application after this change & check the server log.In case u r not able to find out the problem,send the stach trace.
    regards
    Sumit

  • LDAP security provider and web service authentication

    Background: we are currently developing web services to our existing weblogic application. Our users can configure user/password authentication in one of three ways: database, LDAP, or SSO. Setting SSO aside, we need to implement the same authentication for database and LDAP that we use in our existing logon servlet in our web services. In our servlet we detect which they are configured for and, if database, authenticate the encrypted password to a database table we have for user id/password. If LDAP we use weblogic.servlet.security.ServletAuthentication and the weak() method to authenticate.
    We've to use SOAP headers to communicate username/password from the client to the web service. We want to code a SOAP message handler to grab the username/password and do the authentication there. We've successfully put something together that handles the database authentication no problem and are now struggling with how to handle the LDAP authentication. We distribute a LDAP security provider we've coded for LDAP authentication. I guess what I am looking for is an equivalent functionality provided with weblogic.servlet.security.ServletAuthentication. Note that I realize the weblogic.servlet.security package has been deprecated starting with Weblogic 9.0 but cannot find what functionality replaces it. Any help there would be appreciated as well.
    Note that I am fairly new to web service development (about 10 months now) and definitely new to web service security and Weblogic security. I tried digging into the volumes of documentation out there regarding these two topics but am simply having a difficult time sorting it all out and figuring out how to do what I want to do.
    Thanks in advance!
    Julia

    Hi,
    Add Provider (LDAP Credentials) in Admin console Security Realm --> defaultrealm -->Providers. Configuring Ldap in Admin Console will enable Admin Server to connect to LDAP. All the LDAP preconfigured Users/Groups will be available in Users and Groups Tab of Security Realms >defaultrealm >Users and Groups. Add Roles using Security Realms >defaultrealm > Roles and Policies > Global Roles > Roles. Add Role Conditions to the role by specifying users/groups configured in LDAP. If your webservice runs with SSL Anotate the Webservice file something like this below.
    @RolesAllowed({
    @SecurityRole(role="test")
    @Policy(
    uri="policy:Wssp1.2-2007-Https-UsernameToken-Plain.xml",
    attachToWsdl=true)
    Here the role is Preconfigired role in AdminConsole. Add the following tag in the soapenv:header.
    <soapenv:Header>
    <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
    <wsse:UsernameToken>
    <wsse:Username>test</wsse:Username>
    <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">password</wsse:Password>
    </wsse:UsernameToken>
    </wsse:Security>
    </soapenv:Header>

  • Simple web service authentication question

    I'm using the application server included with Sun ONE Identity Server 6.1 (and Apache Axis) to deploy a very simple sample web service. Accessing it from a web browser works fine. (After entering the url to my service, I'm redirected to the authentication page. After authenticating, my service is executed as expected.)
    The problem comes when I attempt to execute this same web service from a Java application (using Apache Axis). I authenticate programmatically and have a valid SSOToken. How do I pass my authentication information along to the IS server when invoking the web service programmatically? Can I do this somehow with the SSOToken I have? Every time I invoke the service programmatically, a "(302)Moved Temporarily" HTML response is received.
    Thanks for your help.
    David

    This solved the problem for me (using Axis):
         call.setProperty(org.apache.axis.transport.http.HTTPConstants.HEADER_COOKIE,
                          "iPlanetDirectoryPro=" + token.getTokenID().toString());
         call.setMaintainSession(true);Hope this helps.

  • Web Service System problem in EP 7.0 SP9

    Hi.
    We used Web Service for VC and CAF.
    For this, We created Web Service System and we used SAP Logon Ticket for authentication in EP 7.0 SP08.
    After we applied SP09, We got authentication problem in web service system.
    From my analysis, I found SAP Logon Ticket is missing for logon method in web service system template.
    Web service system template in EP 7.0 SP09 only has "NONE", "USERID/PWD" for logon method.
    How can we use SAP Logon Ticket for web Service System ?
    Regards, Arnold.

    Hi,
    it's simple: your portal version does not support IE7. To get it working, upgrade your portal to a supported SP. There is no workaround. The EP heavenly depends on Javascript, and IE7 won't run correctly the JS from SP9.
    br,
    Tobias

  • Web service reference problem

    Hi, I am trying to create a web service reference from Windows Dynamic CRM web services. CRM uses windows authentication. I can open WSDL file with IE and firefox. But the same username and password don't work with APEX.
    Does anyone have a clue? Many thanks!
    Crystal
    Edited by: user8991541 on Aug 4, 2010 8:40 AM

    I was able to resolve the problem -- in the latest version of the RESTful web service that I created, I had left out the creation of the Header Parameter bind variable. Once I did that everything works fine!! I was able to test in the application and got the record of an individual student.
    Thanks,
    PM

  • MDM Web Service authentication issue. How to use ?

    Hi,
    I' am a Microsoft technology person I' am working on integrating SAP MDM 7.1 to SharePoint 2010 using MDM Web Services interface and consuming the same in .NET custom component.
    I tried the WS with "None" authentication and it worked great.
    I' am having issues understanding how HTTPAuthentication with SAP Logon ticket authentication works in MDM.
    Created the authentication enabled web service and while testing in NetWeaver WS Navigator, it throws me exception, not able to establish session with repository for user XYZ.
    Please help me with the following queries I have:
    1) How to test a authentication enabled web service in NetWeaver WS Navigator ? Do the user id/password needs to be set in the "Invocation Parameters" ? Link to any article etc will be appreciated.
    2) How to pass the MDM user credentials (or just the username) in the MDM web service in .NET code. I didn't see any parameter in the Client class constructor to pass the same, nothing related to that found in the code that gets generated on adding the service reference.
    As per the documentation on the MDM security, looks like a trust relationship also needs to be configured on MDM - allow.ip file entries.
    However first I want to understand how to pass this information in Web Services through code.
    SharePoint   -
    (1)--> SAP PI  -(2)--
    > SAP MDM                                             
    (integrated with Active Directory                        (Where Web services are deployed     (have its own user accounts)
    so logged in user is already authenticated)          and have its own user accounts)
    The trust relationship configuration could solve the problem of authentication marked in second hop (2) by registering the IP address of PI server.
    Please help me understand how would it work to solve the first hop (1) problem and what needs to be done.
    Thanks,
    Parvinder

    Thanks Gaurav.
    The link talks about setting up the Trust with MDM server.
    The code sample provided there has the following step where user name is being set and passed to MDM:
    Use  command to authenticate user session on trusted connection
           TrustedUserSessionCommand  tuscTrustedUser =
           new TrustedUserSessionCommand(mySimpleConnection);
           //  Set the user name to use
           tuscTrustedUser.setUserName(UsernameAsString);
           tuscTrustedUser.setSession(session);
           tuscTrustedUser.execute();
           session =  tuscTrustedUser.getSession();
    I want to understand how to do that for MDM Web Services.
    I didn't see any method accepting this user name while calling the web service method / creating client object.
    So that link is still missing.
    Appreciate if anyone can help me with that.
    This is for MDM 7.1
    Thanks,
    Parvinder

  • Consuming Web Service | Authentication

    Hello Friends,
    I'm having some trouble configuring a Web Service regarding authentication.
    I created a remote function in SE80 and a web service with it, then I went to SOAMANAGER and configured the authentication section with the 'no authentication' option and added the user/pass in the 'ABAP Service User'.
    In SICF the service is active and seams OK(the user/pass is set), but every time I try to open the WSDL in the browser I get 'A username and password are being requested by SAP Web Application Server'...
    I tested the service with SOAPUI and it also requests the User/Pass for SAP, so it seams that the problem is to enter in SAP WAS and not to access the web service.
    Please advice.
    Thank you.
    PT

    Hello Paulot,
                         You are confused with the WSDL URL and the Webservice Binding URL.
    WSDL URL :
                      This gives the description about the Interface defination for that Webservice interface and it also contains the Binding url in the SOAP Address tag . This the the url , whick will be called on consuming the webservice from external interfaces.
    Binding URL:-
                    This is the URL , whick will be called on consuming the webservice from external interfaces.
    Let me know if you ahve any questions.

  • Web Service calling problem over XI

    1- We prepared message uses web service in XI system
    2- We generated proxy object in R/3 side.
    The proxy object runs properly some locations of network and does not run other locations of network. But SAP R/3 runs properly all locations of network.
    We want proxy object run properly all locations of network.
    Why is this problem occurs?
    Thanks.

    Hi Amitabha,
    <u><b>SOAP Receiver definition in  XI Directory Configuration</b></u>
    <b>Transport Protocol:</b> HTTP
    <b>Message Protocol:</b> SOAP 1.1
    <b>Adapter Engine :</b> Integration Server
    <b>Target Url:</b> http://brckxidb:82/insBLkapi/inserttblbrc.asmx
    <b>Configure User Authentication</b> (checked)
              <b>User :</b> username
              <b>Password:</b> password
    <b>Configure Proxy</b> (Not Checked)
    SOAP receiver definition given above has Configure Proxy item not checked.
    If I decided use to proxy configure checked, that time must I use brckxidb as proxy host and 82 as port?
    Thanks for your help
    <b>SOAP Action:</b> http://tempuri.org/GetData

  • WS-Security, WSE, Web Services, Authentication and Flex 2

    Hey All,
    I've been working hard on getting Flex to communicate with a
    Microsoft .NET 2.0 Web Services project enabled with WSE 3.0
    WS-Security. I can't seem to get the headers into the SOAP request
    that I need.
    For example, I can get a SOAP header into the message like
    so:
    <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>
    <ns0:Security xmlns:ns0="
    http://tempuri.org/">
    <ns0:password>pass</ns0:password>
    <ns0:username>DOMAIN\Administrator</ns0:username>
    </ns0:Security>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
    <HelloWorld xmlns="
    http://tempuri.org/" />
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    .. but, this isn't what my WSE, WS-Security enabled service
    expects. Which is:
    <soap:Envelope xmlns:soap="
    http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="
    http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="
    http://www.w3.org/2001/XMLSchema"
    xmlns:wsa="
    http://schemas.xmlsoap.org/ws/2004/08/addressing"
    xmlns:wsse="
    http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
    xmlns:wsu="
    http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
    <soap:Header>
    <wsa:Action>
    http://tempuri.org/HelloWorld</wsa:Action>
    <wsa:MessageID>urn:uuid:5be8b55a-df7b-4547-8def-76282fcd8b47</wsa:MessageID>
    <wsa:ReplyTo>
    <wsa:Address>
    http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>
    </wsa:ReplyTo>
    <wsa:To>
    http://localhost/CampaignMojoAPI.asmx</wsa:To>
    <wsse:Security soap:mustUnderstand="1">
    <wsu:Timestamp
    wsu:Id="Timestamp-aab299a8-81e3-4d8a-bfa4-555f38978584">
    <wsu:Created>2007-06-06T20:26:37Z</wsu:Created>
    <wsu:Expires>2007-06-06T20:31:37Z</wsu:Expires>
    </wsu:Timestamp>
    <wsse:UsernameToken xmlns:wsu="
    http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
    wsu:Id="SecurityToken-b43668b1-51a3-4ba1-a90a-69eca3b98b66">
    <wsse:Username>DOMAIN\Administrator</wsse:Username>
    <wsse:Password Type="
    http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#Passwor dText">pass</wsse:Password>
    <wsse:Nonce>IK4ZemfS1pj3kpdYO5+FBg==</wsse:Nonce>
    <wsu:Created>2007-06-06T20:26:37Z</wsu:Created>
    </wsse:UsernameToken>
    </wsse:Security>
    </soap:Header>
    <soap:Body>
    <HelloWorld xmlns="
    http://tempuri.org/" />
    </soap:Body>
    </soap:Envelope>
    I've tried "addSimpleHeader" and "addHeader", but both seem
    to inject nested xml elements. Can anyone help me shape this WS
    call into the format I need it in? Would it be possible to call
    this WS manually via a direct HTTP post from Flex 2?
    Thanks!,
    Sean

    Yeah,
    Hey guys - thanks for the responses. I looked into this and
    it seems no one uses WS-Security from the browser. That's why even
    Google's APIs use alternative key logins, etc. I read from one user
    that in the next version of Microsoft's AJAX platform that they
    might support it, but that's about it. For now, it looks like
    there's not even an AJAX/Javascript way to do this. If we could do
    it via Javascript, then we could use the FABridge. I don't think
    Flex supports it. I've tried to manipulate the headers into place
    via Flex classes and I don't think enough control is there to get
    the output in the form that's needed.
    I think it's possible to write it in Javascript. But right
    now my time budget just doesn't allow for it. I already spent two
    whole days re-writing how Flex makes Web Service calls so they're
    synchronous with timeouts instead of this massive amount of
    asynchronous code they want you to write, so no more
    re-writing/extending of components for me for a while.
    But if anyone wants to work together to support it via
    AJAX/Javascript, I would invest money into developing it.
    I would like a public WS-Security AJAX/Javascript framework
    for making these calls via WS-Security so I can offer customers a
    standard way of accessing/authenticating against our public API
    set. It would also make it possible for Flex to access standard web
    services with WS-Security enabled.
    Let me know what you guys think, or if anyone else has any
    good suggestions/software.
    Thanks much,
    S.

Maybe you are looking for