To enable front ends to sign and encrypt documents, maintain the SSF data for the user.
The security product has been installed and SSF has been configured on the application server.
You have defined the location of the SSF RFC server program ssfrfc as the RFC destination SAP_SSFATGUI in Configuration of RFC Connections (transaction SM59).
The user SSF information is included in the standard user address information.
To maintain the user SSF information, use the appropriate transaction as shown in the following table:
Transaction |
User Role |
Task |
---|---|---|
SU01 |
System administrator |
Set up and maintain user master records for all users, including the SSF information for users. |
SO12 |
Office administrator |
Maintain the office information of users, including the SSF information of users for using digital signatures. |
SU3 |
User |
Maintain his or her own address information including SSF information for receiving encrypted data. |
Field |
Available with Transaction |
Description |
Comment |
||
---|---|---|---|---|---|
SU01 |
SO12 |
SU3 |
|||
SSF-ID |
Yes |
Yes |
Yes |
SSF user name |
The syntax of the SSF user name is determined by the security product that you use. |
Profile |
Yes |
No |
Yes |
Profile name |
Specifies the profile where the security information of the user is stored. The value of this parameter is also determined by the security product that you use. |
Destination |
Yes |
No |
Yes |
The RFC destination (logical destination) where the SSF RFC server program has been defined. |
See the input help (F4). Default is SAP_SSFATGUI (SSF for digital signatures on the front ends). |
You can only maintain those fields that are available in the specific maintenance transaction. (See the Available with Transaction column in the table above.) The applications only display the relevant fields. For example, the office administrator, who uses transaction SO12, cannot change the individual SSF profile for a user.