SM59 logon & security tab

[anuj_srivastava]

Hi ,

Do anybody have any idea what we have to maintain in the tab 'Logon & Security ' in the tcode sm59 in the field 'Authorization For Destination '.

Regards,

Anuj

[Former Member]

Hi,

SM59 is used to maintain RFC Connectors,

In Logon & Security' , they maintain a userid and password which is used to login to SAP client, for example if from 720 client you have to run a RFC FM in 740 then you use the RFC Connection for 740 client and login to that client and run the FM.

Regards

Kumar M

[anuj_srivastava]

Hi ,

Where will we maintain the user is and the password ??

[Former Member]

hi,

in logon & security tab only

in logon box

client---

userid---

password---

enter these details

and press remote logon after saving the datails.

Regards,

R K.

[Former Member]

U give the userID and password of the system and client that you have created RFC destination for connection the specified system(IP/host) in the techincal setting tab.

With user ID and password to connect to system remotely

[Former Member]

Hi Anuj,

In SM59, after clicking on Security/Logon tab you need to enter the following details.

Language : EN

Client : Client number of the system (Ex:500)

User : Username of the targer system to which you are getting connected.

Password : Password of the above username in the target system.

Save the screen once you are done with the above information.

You can check the same by clicking on Remote Logon button on the application bar.

You should see the screen of the target system after clicking the above button

Hope the exaplantion is crystal clear

Thanks,

Babu Kilari

[anuj_srivastava]

Hi ,

I cannot see the tabs for following.

Language : EN

Client : Client number of the system (Ex:500)

User : Username of the targer system to which you are getting connected.

Password : Password of the above username in the target system.

can u suggest why ??

[Former Member]

Anuj,

First of all tell me what is the procedure you have followed to create RFC Connection.

If you have selected RFC Connection type as R/3 then you should see the tab that I have mentioned above.

Please confirm first

Thanks,

Babu Kilari

[Former Member]

hi,

maybe you are not given full authorization ... please check with basis consultants

Regards,

Sidddarth

[Former Member]

Hi Sidharth,

I dont think so. If he has access to SM59 transaction, then he should be able to do that.

Thanks,

Babu Kilari

[anuj_srivastava]

I have selected connection type as T.

[Former Member]

Anuj,

You will have to select Connection Type as '3' if you are connection two SAP Systems.

Thanks,

Babu Kilari

[anuj_srivastava]

Hi ,

In my case i am calling a exe file from my abap code and exe path is defined in that RFC.

For that case when i am running the code i have to manually log onto the server(not SAP server but a IP address) for 1 time and then it will work fine.

My question is why it is reacting like this ??

[Former Member]

hi,

with the tcp/ip connection that is type 'T' connection from your system in sm59 does not ask for login details..

so the SAP system does not know with which id it should logon and what should be the authorization in that

system after its logged on....

so the first time you get connected to the RFC, it gets the credentials from the user for the first time and then

it uses the same credentials to login and does not ask the user to login again

Regards,

Siddarth

[anuj_srivastava]

Thx all..

[Former Member]

I understand that your question is closed, but the answers are not particularly usefull... so I wanted to add a comment.

This controls both the ability to administrate the RFC destination (object S_RFC_ADM activities) and the ability to call the destination as a "client side" security mechanism (object S_ICF activities).

If the value is maintained in SM59, then these optional objects can be used to isolate sensitive connactions both from being changed within SM59 and from being called (from programs, services, SE37, etc).

It is a very usefull mechanism, as the RFC connection even if restricted will still be able to do that which it is authorized to do. So you can restrict who can use that context, regardless of the authority of the user in the connection - but not regardless of the caller (the admin or the end user).

Cheers,

Julius