HTTP error 500 User not authorized

[Former Member]

Hi

I have a scenarion file->XI->Proxy.

For that i have created a HTTP connection in SM59.But when i am testing the connection i am getting the following log.

HEADER NAME HEADER VALUE

response_line HTTP/1.0 500 User not authorized for message processing

server_protocol HTTP/1.0

status_code 500

status_reason User not authorized for message processing

ontent-type text/xml

ontent-length 838

ontent-id <soap-0037894A3B5D874EA0C7F1135DBBD904@sap.com>

oapaction 'http://sap.com/xi/XI/Message/30'

erver SAP Web Application Server (1.0;640)

remote_addr

uri_scheme_expanded NONE

HTTP BODY

SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">#<

OAP:Header>#</SOAP:Header>#<SOAP:Body>#<SOAP:Fault xmlns:SOAP="http://s

hemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><fa

ltstring>User not authorized for message processing</faultstring><fault

ctor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xml

s:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmls

ap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIProtocol

/SAP:Category><SAP:Code area="MESSAGE">NOT_AUTHORIZED_FOR_PROC</SAP:Cod

><SAP:P1>DKAUSHAL</SAP:P1><SAP:P2/><SAP:P3/><SAP:P4/><SAP:AdditionalTex

/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>User DKAUSHAL h

s no authorization to process messages##</SAP:Stack></SAP:Error></detai

></SOAP:Fault>#</SOAP:Body>#</SOAP:Envelope>#

Time (ms) 31

Can anyone faced this problem.Please suggest me how should i fix it?

Thanks

Debraj

[Former Member]

Hi Debray,

1. Did you get an error when testing the HTTP Connection from R3 to XI??

2. when creating the HTTP connection did you specify path prefix /sap/xi/engine/type=entry

For this connection you can use the standard XIAPPLUSER.

cheers,

naveen

[former_member184154]

It's XI connecting to R/3, not viceversa...

[Former Member]

>>i have a scenarion file->XI->Proxy.

if the scenario is XI to abap proxy there is no need to have a HTTP connection unless its an RFC call instead of Proxy.

I could have got it wrong

Cheers,

Naveen

[former_member184154]

That's not correct. Indeed you need a Receiver Channel of type XI Adapter (which is basically an HTTP connection) pointing at the R/3 business system, and there you need to put an R/3 user that can (from an auth. viewpoint) process Inbound Proxy calls (and all the other required auth, e.g. for a specific bapi call).

The problem here is to know exactly which role/profile is needed by the R/3 user to be able to process inbound proxy call.

[Former Member]

Alessadro,

You are correct , During configuration there is a need ofr Reciever Channel of type XI adapter. I got it all mixed up when i saw

>>For that i have created a HTTP connection in SM59 in >>the initial post.

>>The problem here is to know exactly which role/profile >>is needed by the R/3 user to be able to process inbound >>proxy call

you are correct there is a need of a user id with right auhorizaions to execute Proxies.

Naveen

[Former Member]

Once again thanks Alex

But the role SAP_XI_APPL_USER is a XI role.And in R/3 there is no such role i found.

If i assign this role to my XI box user id which is of same in the R/3 will it work?

Thanks

Debraj

[former_member184154]

> But the role SAP_XI_APPL_USER is a XI role.And in R/3

> there is no such role i found.

That's odd. What WAS version is under R/3? If it's 6.20, do you have <b>APPINT component</b> being imported?

> If i assign this role to my XI box user id which is

> of same in the R/3 will it work?

Nope. You should have something very similar in the R/3 box (unfortunt. as I said I got no instance where to check 4 u). And anyway, if you're not going live and not having too-much-security-restriction, try assigning SAP_ALL profile to the R/3 user connecting from XI.

Let me know.

Alex

P.S. If you are annoyed by sysadmin, create a new RFC (Communication) user in R/3 with SAP_ALL, so that you can use it for http/rfc communication but not for logon, which should make sysadmin easier.

Message was edited by: Alessandro Guarneri

[Former Member]

Thanks Alex

For so early reply.

But i have doubt.Suppose i am conncting XI with SAP using HTTP Conncetion.In the Log on data tab of HTTP conncetion ( SM59 transaction ) the user id and password of SAP system should be entered.And that has to be a SAP_XI_APP_USER role assigned is that so?

Please suggest me.

Also when the connection will be success what will be the staus code for success.

Thanks

Debraj

[former_member184154]

Hi again,

> In the Log on data tab of HTTP

> conncetion ( SM59 transaction ) the user id and

> password of SAP system should be entered.

Sure.

> And that has

> to be a SAP_XI_APP_USER role assigned is that so?

Sounds good. It's worth give it a try. This is a role for the R/3 user of course.

> Also when the connection will be success what will be

> the staus code for success.

Mmmh, not sure. Because you'll always be sending something empty from SM59, I guess R/3 ICM will respond badly... Kinda "empty message received" error...

But don't you worry. Just try the real thing!

Cheers,

Alex

[former_member184154]

Quite simply it seems that the R/3 user you put in XI configuration doesn't have enough rights. Can you try with a SAP_ALL user? That should temporarily solve your problem. In the meantime I'll search for adhoc role/profile.

Alex

[former_member184154]

Sorry I don't have an R/3 with WAS >= 6.20 on hand...

Try go to PFCG of your R/3 env, and search for an XI role with keywords like "message" "processing" or "proxy".

Hope this helps.

Alex