Service Type User ids

[Former Member]

Dear SAP Security Gurus,

We use service user type for test user ids in our test (Q) system. Since service ids can have multiple logins, can you help us know that how many users can login with a service id at the same time?

Thanks,

Karthik.

[martin_voros]

Hi,

I don't think that there is a limit but I think that you do it wrongly. There is no reason why you should use service type users if you want to have multiple users. Have a look at parameters login/disable_multi_gui_login and login/multi_login_users. First one allows you control if dialog users can have multiple logons. The second allows you to create a subset of users (e.g. testing users) with allowed multiple logons. MOre info about these parameters in RZ11.

Cheers

[Bernhard_SAP]

do you think that this is a good idea to allow multiple logons? (how to track changes etc?)

Please have a look at

http://forums.sdn.sap.com/click.jspa?searchID=45376694&messageID=9012003

One good point is always the licensing....

Did your responsible SAP subsidiary agree with the usage of multiple logins with the same ID?

b.rgds

Bernhard

[Former Member]

Hi Karthik,

Look into transaction rz11 to the parameter login/multi_login_users.

BUT I agree with Bernard, do not do such things if possible and it is possible.

have fun

Bye

Jan van Roest

[Bernhard_SAP]

Hello Jan,

login/multi_login_users:

Parameter description :

This list contains the R/3 user IDs (clients not specified)

allowed to log on to the system multiple times.

(Caution: Special entry format, see below)

This profile parameter only applies for dialog users.

so this parameter will not help Karthik regarding Service users

b.rgds, Bernhard

[Former Member]

One reason why he is probably doing this in the training system is to avoid numerous password resets and lock/unlock due to multiple users using the dialog user ids.

Wrong practise but saves lot of effort if you do not have licensing or any compliance issues.

[Former Member]

Folks ... My response is structured as :first Licenicing and then Service user :

Karthik was mentioning ablout the Q system ..Are users on the Q system charded as well ..yes a non commital answer is " it depends on the agreement "!! As I understand in my very very limited experience that the user count and licensing is done on the PRod system. here again I can be wrong..as very often I am!

Now on service users !!

Dear Karthik ...as it was pointed out...why do you need service user in Q ?? how can you log the changes ?? the results will be cumbersome to evaluate

User A will use test case 1 /User 2 test case 3 / now for example you have an auth issue which ID will the security admin trace ? as User A & User B both use the same ID !! -- hope it sclear ..please use Dialogs and help your security admin !!

[Former Member]

Hi George,

Thanks very much for the information and suggestions. Actually we do not use service for integration test,. We are using service ids only as training ids. These training ids will not be testing anything and therefore we are ok with having service ids. All I wanted to know is how many users can simultaneously login in to a service id at the same time.

Thanks,

Karthik.

[Former Member]

Hi Karthik,

Check out the documentation of parameter "login/disable_multi_gui_login":

 This parameter works with SAPgui logons.
System logons using the Remote Function Call (RFC) are controlled
using the parameter %%login/disable_multi_rfc_login%%.
*Logons with SERVICE user master records are also not subject to the
mulitple logons check * 

Hence it doesnt seems to me that there is any limit to it.

[Former Member]

Karthik,

Nice to hear that there is no limit ..actually its a good idea if you can suggest to your company to limit it using the parameter mentioned in the threads. You may get a feather on your cap too !! ( or a slap on ur cheek !!) Either way you will get somethign !

I didnto know that there is no limit ....thanks for the info.

Thanks

[Former Member]

Team,

There is no limit on how many people can login to a service id.

Thanks,

Karthik