on 05-28-2009 12:26 PM
Hi there,
I am trying to define JAVA-authorizations in our PI-landscape. My recent problem is that I am trying to give our developers the opportunity to read message payloads in the Runtime Workbench.
So far I have only been able to do this with administrator rights and this is no option. In the future I'd even have to distinguish between authorizations for different types of messages (according to namespaces et cetera) like you can do it in ABAP via the authorization object S_XMB_MONI, but first I'd like to at least assign payload authorizations without administrator rights.
Any ideas?
Regards
Mario
http://help.sap.com/saphelp_nw04/helpdata/en/89/05793c05f0807be10000000a11405a/content.htm
role SAP_XI_MONITOR should do the trick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The correct note-number for PI 7.1 "Securing Payloads in Message-Monitoring" is: 1370334
Regards,
Max.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for your answers, but that's not really enough for us. We are already able to restrict the message monitoring regarding header data and payload. What we really want is to seperate the payload authorizations like you can do it in ABAP with the S_XMB_MONI object, so different users are able to view different message payloads.
Any idea on how that could be accomplished would be highly appreciated!
Regards
Mario
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My last information concerning restricted payload access in the java engine on interface or namespace level is that this is not possible. You can only give the right to access the payload or you deny it. You cannot configure it as detailed as you can in the ABAP stack with the object S_XMB_MONI.
If someone developed custom actions in the UME, please update this thread. I'm interested too in restricting the payload access in the java stack more detailed.
Regards,
Heinrich
Dear Satish,
maybe I misunderstand the blog entry. But how is that supposed to help me separate the viewing authorizations for payloads in the Runtime Workbench? The way I understand it this provides a way to restrict access to services, which is a nice thing, too, but not what I was looking for...
Regards
Mario
Check this SAP Note on what you need to do inorder to enable the user with the view, edit functionality of the payload in RWB:
https://service.sap.com/sap/support/notes/796726
Regards,
Abhishek.
Mario,
Check this document. Hope this helps:
Regards,
---Satish
>
> Now that's a little better as it at least deals with viewing authorizations. But as I said before, we've already accomplished that in the ABAP stack. Now I'd like to know how to do this in the Runtime Workbench, but I guess it's just not possible right now...
there is no configuration to be done in RWB.....however there is some in the VA (i.e. the JAVA stack)....check the note which i have provided in previous reply...
Regards,
ABhishek.
I still don't think you understand me. I want certain users to be able to view the payload of namespace A and other users to be able to view the payload of namespace B. As far as I know (and according to what other people said in this thread) you can just view payloads or don't view payloads, except if you develop your own actions.xml - which I tried, too, but without any success so far...
Hey
Please have a look at the below link to see how you can restrict access in Integration engine as well as adapter engine
http://help.sap.com/saphelp_nw04/helpdata/en/a0/64f6413a15e23ee10000000a155106/frameset.htm
Thanks
Aamir
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.