SAML2.0 for web services - sender-vouches scenario

We would like to configure this scenario using SAML2.0 assertion tickets. We are on ECC 6 EhP6.
Configuration in SAML2 has been completed - no WS security policy has been configured in order to support the sender-vouches scenario.
WSS_SETUP has run to use SAML.
When configuring the web services we are using https for transport and SAML for authentication - the wsdl generated in this case references SAML1.1 and as result we get an error of Wrong token type received. Endpoint expects SAML 1.1 token.
The question is: can SAML2.0 be used for sender-vouches scenarios or not?
Any input or help would be greatly appreciated.
Thank you,
Miklos

Hi Miklos,
Yes you can use SAML2.0 for Sendor-vouches scenarios.
Please see the below link for configuration process:
http://help.sap.com/saphelp_nw73/helpdata/en/b5/014086933d4576bba1b4c7e9533f4b/content.htm
I hope it will be helpful for you.
Regards,
Gourav
Message was edited by: Gourav Kumar Jena

Similar Messages

Web Service to FTP scenario - MAPPING.NO_MAPPINGPROGRAM_FOUND error

Hi,
I am developing a Web Service to FTP scenario in XI, I am testing the interface by writing a client program using AXIS. when I invoke the service from the client, it is able to hit the service and writing the file to FTP with the data However the client is program receiving a fault with the below error.
"SystemError:<context/><code>MAPPING.NO_MAPPINGPROGRAM_FOUND</code><text>Unable to determine name of mapping program</text>"
I set quality of service to 'Exactly Once' on the SOAP sender adapter.
Would appreciate any help on this.

Hi,
What is the URL to which you are posting the SOAP message?
Is it?
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet? channel=<party>:<service>:<channel>
If yes, then like mentioned the QOS is picked from the Sender SOAP adapter.
But, if the URL is ,
http://<server>:<ABAP-port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<YourService>&Interface=<YourNamespace>%5E<YourInterface>
Then you need to give the QOS as <b>,&QualityOfService=ExactlyOnce</b> appended to the above URL.
More, /people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
Regards
Bhavesh

Web Service to IDoc scenario: No receiver could be determined error

Hi. I am working on a web service to IDoc scenario. I am receiving this error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I've taken the XML message being sent to me and tested the mapping and I've completed the test configuration in the IB. Both work fine. Any ideas? I've been looking into this for a couple of days, so I've been through all the previous posts I could find.
Thank you.
Nicole

hi,
This is not related to receiverdetermination ,whether you creaeted or not.
It is somthing related to receiver systemwhich was configured in Receier determination.
check the target BS is correct or not or the inbound interface.
Did you configured the proper receiver technical system..
OR
Check the Receiver Determination is configured correctly. i.e R/3
Verify all the configurations like SM59, Partner Profile/Logical systems. etc. Also check in SM58 of R/3 system.Make sure that All the objects are activated in the Directory.Refresh the cache.Verify is the business system is pointing to correct R/3 system . Go to Business system/Service->Menu->Adapter specific identifiers in the directory
You can test your configuration with sample
payload.
In ID goto to TOOLS -
> Test Configuration for testing.
Hope in this way you can still find at which point the interface goes wrong.

WEB SERVICE TO ORACLE SCENARIO

Hi all,
I have to develop a web services to Oracle scenario. My problem is that I need to executed selects and stored procedure at runtime in the mapping. I mean that i need to check some values from the inbound during the mapping execution I did that before in Sap R/3 but i don´t know how to execute it in a Database.
Many thanks for your help!!!
Regards
Noelia

hi,
you can use standard API to do this lookup in
the mappings:
/people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

XML really that crucial for Web Services?

No doubt Web Services are here to stay. I've tried to learn about them by reading different sites on the internet. But so far, I've only been able to read positive praises of XML. Such as the buck-a-car system. However, I'm interested in some of the negatives of XML. I want to know where XML will NOT work and is discouraged. Only be considering the negatives and limitations can I understand whether XML is appropriate for my system. (e.g., is XML good for database-to-database communications?)
When I look at the average XML file, there is so much overhead such as the DTD and descriptive XML tags. If one XML file was used to store a lot of information, it would be acceptable. But if I were to say, write a chat program, it doesn't seem wise to send an XML file for each sentence/letter typed.
And if I wanted to synchronize two databases through the internet, wouldn't it be faster to just send each record as a stream of bytes and have the other database parse that? Instead of converting the record to XML and back.
Or if I was communicating between the server and an applet, should I convert all requests into XML even though I am well aware of the format of the applet?
I personally see XML being used in only a small number of applications such as an initial handshaking process before communications.
I know it must be because I have a lack of understanding. If anyone has comments or even agrees, your feedback is more than welcome.

Well of course XML is crucial for Web Services, because the messages they pass back and forth are in XML format. (Of course that's only for the current buzzword "Web Services", some of us have been producing Web Services where the messages are in e-mail format for years now.) You're right, using XML for everything is stupid. And if you control both ends of the conversation, you can talk in any language you like, and you probably should. But if you want to talk to large numbers of people, and you don't want to limit what kind of data you might send, then you need a standard framework to do that, and XML is it. That doesn't mean that XML will replace SMTP or any other existing standard format, just that it's likely to be widely used in the future for sending generalized data between systems.

Re: Why doesn't WL7.0 support get/post bindings for web services ...

hi!!!
Could you pls point to any code example.
thanks
Pushpa
"Richard Berger" <[email protected]> wrote:
>
Manoj: Thanks for the answer - do you have or can you point me at any
code samples
that accomplish this? (Yes, .NET is limited to strings/ints in their
get/post
bindings).
Thanks so much!
RB
PS - Also, can you explain any apparent discrepancy between your answer
and what
the WL documentation stated (again, it may be my misunderstanding).
"manoj cheenath" <[email protected]> wrote:
WL 7.0 does allow you to access the web service through
the browser. It even allows you to invoke service methods
with complex type arguments (.Net only supports primitive
types) and also to view the request and response soap
message for the invocation.
regards,
-manoj
"Richard Berger" <[email protected]> wrote in message
news:[email protected]...
This might be a naive question, but according to the documentation,WL 7.0
does
not support http post/get bindings for web services. Thus, for meto
access a
web service, I need to write a "middle tier" of some sort (I used
the
automatically
generated Java proxy code and JSP). All works fine, but it seems
like
it
would
sure be nice to have HTML forms access web services without havingto
write a
middle tier.
NET does this and it is extremely useful - is there a reason that
BEA
chose not
to provide this feature? (e.g. is it architecturally unsound in anyway?
or is
there an easy way to simulate it?). Given some of the Web Workshoppositioning
re: ease of use and .NET comparison, this seems like an omission.
Any insights are greatly appreciated.
Enjoy,
RB
PS - Here's the info from the documentation
Web Services Description Language (WSDL) 1.1 Specification
WSDL is an XML-based language that describes Web services. WSDL definesWeb services
as a set of endpoints operating on messages; these message containeither
message-style
or RPC-style information. The operations and messages are describedabstractly
in WSDL, and then bound to a concrete network protocol and messageformat
to define
an endpoint. Related concrete endpoints are combined into abstractendpoints (services).
WSDL is extensible to allow the description of endpoints and theirassociated
messages regardless of what message formats or network protocols areused
to communicate,
however, the only bindings described in the specification describehow to
use
WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.
Note: WebLogic Server supports only SOAP 1.1 bindings.
The WSDL 1.1 Specification is available at http://www.w3.org/TR/wsdl.

This isn't a straight FORM Post as in the http binding support in WSDL. It posts
a soap message.
It's apparent that Workshop supports form-post and form-get.
But I dont see how it is done with straight WebLogic webservices. Does WebLogic
server read the web-services.xml or the WSDL file? I dont see a way to put in
http-post binding in the former and in the latter it seems to be ignored.
Can someone clarify.
Thanks.
Chu-chi
"manoj cheenath" <[email protected]> wrote:
Here is a live example:
http://65.193.192.35:7001/base/SoapInteropBaseService
Here is an example that you can download:
http://manojc.com/?sample2
This is how you run it:
http://manojc.com/?tutorial/doc/howtorun.html
More info can be found from the edocs:
7.0:
http://edocs.bea.com/wls/docs70/webserv/index.html
8.1:
http://edocs.bea.com/wls/docs81/webserv/index.html
Regards,
-manoj
http://manojc.com
"pushpa krishna" <[email protected]> wrote in message
news:[email protected]...
hi!!!
Could you pls point to any code example.
thanks
Pushpa
"Richard Berger" <[email protected]> wrote:
Manoj: Thanks for the answer - do you have or can you point me at
any
code samples
that accomplish this? (Yes, .NET is limited to strings/ints in their
get/post
bindings).
Thanks so much!
RB
PS - Also, can you explain any apparent discrepancy between your answer
and what
the WL documentation stated (again, it may be my misunderstanding).
"manoj cheenath" <[email protected]> wrote:
WL 7.0 does allow you to access the web service through
the browser. It even allows you to invoke service methods
with complex type arguments (.Net only supports primitive
types) and also to view the request and response soap
message for the invocation.
regards,
-manoj
"Richard Berger" <[email protected]> wrote in message
news:[email protected]...
This might be a naive question, but according to the documentation,WL 7.0
does
not support http post/get bindings for web services. Thus, for
me
to
access a
web service, I need to write a "middle tier" of some sort (I used
the
automatically
generated Java proxy code and JSP). All works fine, but it seems
like
it
would
sure be nice to have HTML forms access web services without havingto
write a
middle tier.
NET does this and it is extremely useful - is there a reason that
BEA
chose not
to provide this feature? (e.g. is it architecturally unsound in
any
way?
or is
there an easy way to simulate it?). Given some of the Web Workshoppositioning
re: ease of use and .NET comparison, this seems like an omission.
Any insights are greatly appreciated.
Enjoy,
RB
PS - Here's the info from the documentation
Web Services Description Language (WSDL) 1.1 Specification
WSDL is an XML-based language that describes Web services. WSDL
defines
Web services
as a set of endpoints operating on messages; these message containeither
message-style
or RPC-style information. The operations and messages are describedabstractly
in WSDL, and then bound to a concrete network protocol and messageformat
to define
an endpoint. Related concrete endpoints are combined into abstractendpoints (services).
WSDL is extensible to allow the description of endpoints and theirassociated
messages regardless of what message formats or network protocols
are
used
to communicate,
however, the only bindings described in the specification describehow to
use
WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.
Note: WebLogic Server supports only SOAP 1.1 bindings.
The WSDL 1.1 Specification is available at http://www.w3.org/TR/wsdl.

Why doesn't WL7.0 support get/post bindings for web services ...

This might be a naive question, but according to the documentation, WL 7.0 does
not support http post/get bindings for web services. Thus, for me to access a
web service, I need to write a "middle tier" of some sort (I used the automatically
generated Java proxy code and JSP). All works fine, but it seems like it would
sure be nice to have HTML forms access web services without having to write a
middle tier.
.NET does this and it is extremely useful - is there a reason that BEA chose not
to provide this feature? (e.g. is it architecturally unsound in any way? or is
there an easy way to simulate it?). Given some of the Web Workshop positioning
re: ease of use and .NET comparison, this seems like an omission.
Any insights are greatly appreciated.
Enjoy,
RB
PS - Here's the info from the documentation
Web Services Description Language (WSDL) 1.1 Specification
WSDL is an XML-based language that describes Web services. WSDL defines Web services
as a set of endpoints operating on messages; these message contain either message-style
or RPC-style information. The operations and messages are described abstractly
in WSDL, and then bound to a concrete network protocol and message format to define
an endpoint. Related concrete endpoints are combined into abstract endpoints (services).
WSDL is extensible to allow the description of endpoints and their associated
messages regardless of what message formats or network protocols are used to communicate,
however, the only bindings described in the specification describe how to use
WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.
Note: WebLogic Server supports only SOAP 1.1 bindings.
The WSDL 1.1 Specification is available at http://www.w3.org/TR/wsdl.

Manoj: Thanks for the answer - do you have or can you point me at any code samples
that accomplish this? (Yes, .NET is limited to strings/ints in their get/post
bindings).
Thanks so much!
RB
PS - Also, can you explain any apparent discrepancy between your answer and what
the WL documentation stated (again, it may be my misunderstanding).
"manoj cheenath" <[email protected]> wrote:
WL 7.0 does allow you to access the web service through
the browser. It even allows you to invoke service methods
with complex type arguments (.Net only supports primitive
types) and also to view the request and response soap
message for the invocation.
regards,
-manoj
"Richard Berger" <[email protected]> wrote in message
news:[email protected]...
This might be a naive question, but according to the documentation,WL 7.0
does
not support http post/get bindings for web services. Thus, for meto
access a
web service, I need to write a "middle tier" of some sort (I used theautomatically
generated Java proxy code and JSP). All works fine, but it seems likeit
would
sure be nice to have HTML forms access web services without havingto
write a
middle tier.
NET does this and it is extremely useful - is there a reason that BEAchose not
to provide this feature? (e.g. is it architecturally unsound in anyway?
or is
there an easy way to simulate it?). Given some of the Web Workshoppositioning
re: ease of use and .NET comparison, this seems like an omission.
Any insights are greatly appreciated.
Enjoy,
RB
PS - Here's the info from the documentation
Web Services Description Language (WSDL) 1.1 Specification
WSDL is an XML-based language that describes Web services. WSDL definesWeb services
as a set of endpoints operating on messages; these message containeither
message-style
or RPC-style information. The operations and messages are describedabstractly
in WSDL, and then bound to a concrete network protocol and messageformat
to define
an endpoint. Related concrete endpoints are combined into abstractendpoints (services).
WSDL is extensible to allow the description of endpoints and theirassociated
messages regardless of what message formats or network protocols areused
to communicate,
however, the only bindings described in the specification describehow to
use
WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.
Note: WebLogic Server supports only SOAP 1.1 bindings.
The WSDL 1.1 Specification is available at http://www.w3.org/TR/wsdl.

Why do I get parsing errors with my WSDL URL for Web Services usage

Hi,
I am puzzled with the errors I get when I want to create a Web Service datastore.
Scenario: I have created a SAP Web Service from CRM using SOAMANAGER. The WSDL URL produced by SOAMANAGER is accessibile when pasting the URL directly in Internet Explorer. WSDL URL [http://UXCIQ0M.WDF.SAP.CORP:50076/sap/bc/srt/wsdl/srvc_CBDCB34C89C29304E10000000A4282C0/wsdl11/allinone/ws_policy/document?sap-client=504]
When using the WSDL URL in the Web Service datastore URL field, I get the error An error occurred while importing metadata: WSDLException; faultcode=PARSER_ERROR: Problem parsing: The element type "br" must be terminated by matching tag "/br". (BODI-1111469) (BODI-1112446)
When I save the WSDL defintion in a local file and use a local file path, I get the errors An error occurred while importing metadata: WSDLException (at /wsdl:definitions/wsdl:portype/wsp:Policy): faultcode=INVALID_WSDL: Encountered unexpected element 'Policy. (BODI-1111469) (BODI-1112446)
My questions:
- Why do I get different parsing errors despite the fact that the XML is the same?
- The WSDL is generated by SOAMANAGER. Shouldn't it work directly when integrating with Web Services generated from an SAP environment?
- Is this related to confiurgation issue? I have set the Job Manager to Support adapter, message broker and SNMP communication
- What is the difference between the datastore of type Adapter and the datastore Web Service? In the white paper [http://www.sdn.sap.com/irj/boc/go/portal/prtroot/docs/library/uuid/20bd5e60-11f9-2b10-2bbb-b5109cceff08?quicklink=index&overridelayout=true] it is mentioned to use the Adapter type to consume a Web Service. It is not clear to me why we have those 2 types.
Thanks & Best Regards
Isabelle

Some updates on this issue, which might help others in the community.
- Data Service doesn't support ws_policy.
- SAP NetWeaver 7.0 SOAMANAGER generate WDSL with ws_policy. In future releases, it is possible to specify not to use ws_policy
- In most cases, replacing ws_policy with standard in the URL directly, works. It doesn't work with Data Services :(.
- Replacing ALL ws_policy in the XML directly is currently the only way to have the WSDL definition being parsed properly by Data Services.

WSDL error during generation of ABAP proxy for web service

Hi friends,
I am getting error during the generation of ABAP proxy object for web service developed in .NET .
Error : Proxy generation terminated: WSDL error (<extension> not supported).
How to make this WSDL file compatible for ABAP proxy.
I have tried to edit WSDL file in XML Spy but did not get any option to replace/remove the tag <extention>.
If any one worked on this. Please help me its urgent.
Thanks and regards,
Shivanand.

HI ,
I am having the same issue!!!
Does ABAP Proxy Generation support <extension> ?
Is there a list available of what is supported and what not (please consider I do not have access to sap notes)?
Thanks

Best book for Web Services

Can you suggest me what's best book for Web Services and XML to study? I'm planning to buy..
Thanks in advance..

Why does it need to be the best one? What would that even mean? Just buy something reputable, like an O'Reilly book, it's not going to be so horrifically poor that you can't learn from it

How to activate trace for web services

Hi Experts,
How to activate trace for web services in SOAMANAGER.
We are not able to view the Payload trace of the error logs.
Can anyone please let me know how to go about this???
Regards,
Ashwini

Hi Ashwini,
The thread below might be useful to you:
[SOAMANAGER - Get the XML generated;
Regards, Trevor

Building client proxies for web services with SOAP attachemtns

Hi all.
I'm currently building a series of web services that take SOAP attachments as
input, but I am unable to generate the java proxies for testing the services via
WebLogic Workshop 8.1. When I attempt to build the proxy, I get the following
error:
Warning: Failed to generate client proxy from WSDL definition for this service.
Suggestion: Please verify the <types> section of the WSDL.
Is there something I need to alter to get this to work, or does workshop not support
client proxies for web services with DataHandler parameters?
Thanks.
-Brian

Thanks for the help. This is my first web service with SOAP attachments, so it
may have been a long time till I realized that.
-Brian
"Michael Wooten" <[email protected]> wrote:
>
Thanks Brian,
The problem is that you are trying to use the "document" soap-style :-)
If you change this to "rpc", you'll should be able to successfully generate
the
client proxy jar. The soap-style property, is at the bottom of the "protocol"
property sheet section, for the JWS.
Regards,
Mike Wooten
"Brian McLoughlin" <[email protected]> wrote:
Sure, sorry about that. Attached is the wsdl for a sample web service
I created
just to test the proxy generation.
"Michael Wooten" <[email protected]> wrote:
Hi Brian,
Would it be possible for you to post the WSDL, so we can see what might
be causing
the problem?
Regards,
Mike Wooten
"Brian McLoughlin" <[email protected]> wrote:
Hi all.
I'm currently building a series of web services that take SOAP attachments
as
input, but I am unable to generate the java proxies for testing theservices
via
WebLogic Workshop 8.1. When I attempt to build the proxy, I get the
following
error:
Warning: Failed to generate client proxy from WSDL definition for
this
service.
Suggestion: Please verify the <types> section of the WSDL.
Is there something I need to alter to get this to work, or does workshop
not support
client proxies for web services with DataHandler parameters?
Thanks.
-Brian

Stub for web service in JSP

How do i embed a scriptlet inside my JSP page for the stub of my web service? is there any examples that i can refer to?
Thanks in advance. ;)

Check out the 2 How To:
9.0.4 / 10.1.2 "How to use OC4J JSP Tags for Web Services" [1].
10.1.3 (preview) "Access J2EE 1.4 JAX-RPC Java Web Services from Web Clients" [2].
Hope this helps,
Eric
[1] http://www.oracle.com/technology/sample_code/tech/java/codesnippet/webservices/wstags/index.html
[2] http://www.oracle.com/technology/products/jdev/101/howtos/jaxrpc/java14_ws_web_clients.html

About XML Parameter for Web Service invoking

I would like to use the XML parameter as the Web Service's input(Attachment is
the XML schema) in WebLogic Server 8 sp1. When I generated the Web Service and
use the WebLogic Server generate test web page to test it, I got Exception. The
WebLogic Server can't constructe the input XML.
The correct XML should look like this:
<ids>
<desc>Description</desc>
<id>1</id>
<id>2</id>
<id>3</id>
</ids>
Is there any one can tell me whether this kind of XML was permitted for Web Service
invoking or not?
[sample.xsd]

Hi Andy,
On the test page, before the invoke of the operation, did it say
something like:

if so, the service itself may be working OK, the deficiency is that the
test page tries its best to determine sample values for the invoke,
however it does not know in this case.
Did you try with a client?
Your XML should be fine.
Regards,
Bruce
Andy wrote:
>
I would like to use the XML parameter as the Web Service's input(Attachment is
the XML schema) in WebLogic Server 8 sp1. When I generated the Web Service and
use the WebLogic Server generate test web page to test it, I got Exception. The
WebLogic Server can't constructe the input XML.
The correct XML should look like this:
<ids>
<desc>Description</desc>
<id>1</id>
<id>2</id>
<id>3</id>
</ids>
Is there any one can tell me whether this kind of XML was permitted for Web Service
invoking or not?
Name: sample.xsd
sample.xsd Type: ACT Project (text/xml)
Encoding: base64

(261936172) Q general Are there seperate logs for web services?

Q<general> Are there seperate logs for web services?
A<general> It does not appear that there are any separate logs for web services.
There is knex.log file that records the errors that occur during deployment of
your .jws files. There is also the standard server log that provides information
about server status - you can write to this programmatically if you wish. There
is also the access.log file which record all the HTTP requests so this might cover
some of your web service requests that are transmitted over HTTP.

Maybe the user has deniad Access to the Runbook, check in Runbook Designer.
Seidl Michael | http://www.techguy.at |
twitter.com/techguyat | facebook.com/techguyat

SAML2.0 for web services - sender-vouches scenario

Similar Messages

Maybe you are looking for