ITS Service using wrong client

[Former Member]

Hello All,

I'm encountering '401 Authorization Error' problems with content server. The service in sicf is configured to use client 400. The profile parameter "login/system_client" is also set to 400. However, for whatever reason.... When I test the service, it defaults to client 800 for authorization.

If I manually specify sap-client=400 in the URL, there is no problem. Is there any other information I can supply to figure out why this behavior is happening? The 401 error is causing problems when uploading data to my repository as well as while running transaction csadmin.

Thank you,

Zach Shay

[former_member194364 · Accepted solution]

You say above:

"When I test the service, it defaults to client 800 for authorization."

Are you testing the service via SICF directly?

To test from SICF

Goto: transaction /nsicf > default host ->

sap -> bc -> gui -> sap -> its -> my_service

o Select Test service from context menu of the service node

i.e: Right Click -> Test Service

This will launch the webgui service in the browser - from here logon

to system again. From the OKFilecode type /n(transaction name)

What are the GUI Configuration settings of the service?

Goto: transaction /nsicf > default host ->

sap -> bc -> gui -> sap -> its -> my_service

Double click on "my_service"

Tab: Service Data -> Button: GUI Configuration

Where have you the client information specified for the service in SICF?

What is the default client value under the "System Logon Settings"?

Goto: Tab: Error Pages -> Tab: Logon Errors -> System Logon: Click the "Configuation Button"

[Former Member · Accepted solution]

Oisin,

Thank you for the help. I re-read through the manual..... The [manual|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/1a/aea9375d79fb7de10000009b38f8cf/frameset.htm] is a bit misleading with the "anonymous logon data" in the Service Data tab. This is how the manual should be documented:

1.) Open the service in SICF
2.) Choose the Logon Data tab
3.) Select "Required with Logon Data" for the Procedure
4.) Specify the Service User you have created
5.) Save

For whatever reason, when using the standard procedure...the default client used by the ITS was neither the currently utilized client nor any configured client (server or login/system_client parameter).

Thank you,

Zach Shay

[Former Member · Accepted solution]

Zach,

Thanks for posting the answer. I had this problem today and your answer fixed it.

Regards,

Christine