Can Communication User Id change its password

[sumedh_urade]

Hello Experts,

Can Communication User Id change its own password and can the password be deactivated automatically even after when its used?

Regards,

Sums

[Frank_Buchholz]

Change password: yes and no

Yes, because the user can call a specific rfc function to change the password.

No, because usually you cannot extend the rfc client to call this function.

Anyway you should use the user type "system" instead of user type "communication". This eliminates any trouble with expired passwords of users which are used by rfc or jco. There does not exit any disadvantage of using user type "system".

Deactivate password:

You can deactivate the password of a user in transaction SU01 or you can deactivate the password pased logon for all users using a profile parameter.

Kind regards

Frank Buchholz

[Former Member]

before changing the password please check if any RFC connection is not maintained with and after changing the password maintain that password in the particular RFC also.

[Former Member]

Note that if either Communication or System users have authorizations themselves for the user management (S_USER_GRP actvt '05' for the assigned user group) then they will both be able to change passwords (including their own if in that group or not assigned to one).

This is different to changing your own password voluntarily or being forced to by system password rules, but it is also a possibility you should ideally rule out (admin auths for RFC to change passwords).

Unfortunately, several RFC functions and transactions make "bogus" checks on exactly this authorization but do not need them. You you need to be carefull with it. Particularly anything relating to Business Parter functions should be very suspect if you find it in an authorization trace - it is not needed.

Cheers,

Julius

Edited by: Julius Bussche on Sep 20, 2011 10:30 PM