Users
The following table lists the attributes used to import user data.
Attributes for Importing Users
Attribute |
Required? |
Description |
Field Name in User Interface |
[User] |
Required |
Delimiter to separate user records. The UME skips empty lines and does not treat them as delimiters. |
Not applicable |
org_id |
Optional |
Name of the company to which the user belongs. The company must already exist. For more information, see Configuring Delegated User Administration Using Companies. |
Company |
uid |
Required |
ID the user uses to log on. |
Logon ID |
password |
Optional |
If you do not include a password for import, the application generates a password. If the password does not conform to the security policy or if you leave the password attribute empty, the application does not import that user. If the user already exists and has a password, the application updates the password so long as it conforms to the security policy.
This attribute is only available for import. It cannot be exported. |
Not applicable |
role |
Optional, multiple |
List of roles assigned to the user, separated by semi colons. If the role does not exist, a the system generates a warning. You can import and export remote role assignments, if the remote roleexists with the same name in the same producer system. Use the following syntax:
gp:/<producer_alias>/<PCD_URL>
role=gp:/ProducerA |
|
$usermapping$: |
Optional |
User ID to which the user is mapped in the system <system_alias>. <system_alias> is the system alias as defined in the portal system landscape editor.
This attribute is only available for import. It cannot be exported. |
|
$usermapping$: <system_alias>: mappedpassword |
Optional |
Password of mapped user in system <system_alias>. <system_alias> is the system alias as defined in the portal system landscape editor.
This attribute is only available for import. It cannot be exported. |
|
$usermapping$: |
Optional |
Any other attribute value required by an external system <system_alias> to which the user is mapped. <system_alias> is the system alias as defined in the portal system landscape editor.
This attribute is only available for import. It cannot be exported. |
|
<namespace>: |
Optional |
Custom field with
the syntax: namespace:name= By default the value is interpreted as a text value. If you want to use a binary value, you must use the base64 encoded value with the prefix {BINARY}.
myApplication:largeUserPhoto={BINARY} |
Same as the custom field namespace and name. |
email_address |
Optional |
The user’s e-mail address. |
E-Mail Address |
first_name |
Optional |
Self-explanatory |
First Name |
last_name |
Required |
Self-explanatory |
Last Name |
accessibility |
Optional |
Used to enable the accessibility of Web Dynpro interfaces for users with special needs. For more
information, see
|
Activate Accessibility Feature |
job_title |
Optional |
Self-explanatory |
Position |
com.sap.security |
Optional |
Organizational unit |
Organizational Unit |
country |
Optional |
ISO 3166 code for the country. |
Country |
language |
Optional |
Java locale for the country. These are formed by the ISO 639 code for the language followed optionally by an underscore (_) and the ISO 3166 code for the country. |
Language |
time_zone |
Optional |
The time zone, either as an abbreviation such as PST or a full name such as America/Los_Angeles.
Do not enter GMT+09:00 (Asia/Tokyo). |
Time Zone |
salutation |
Optional |
How the user is addressed. |
Form of Address |
street |
Optional |
Self-explanatory |
Street |
city |
Optional |
Self-explanatory |
City |
state |
Optional |
Self-explanatory |
State/Province |
zip |
Optional |
Self-explanatory |
ZIP/Postal Code |
telephone |
Optional |
Self-explanatory |
Telephone |
fax |
Optional |
Self-explanatory |
Fax |
mobile |
Optional |
Self-explanatory |
Mobile |
department |
Optional |
Self-explanatory |
Department |
cert |
Optional |
You can import the user certificate. Enter the certificate encoded in Base 64 with the prefix {X.509}-----.
Do not enter linebreaks. |
|
Accessibility in the
Portal
For the telephone, fax, and mobile phone fields, the following rules apply:
· Valid characters are: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, (, ), +, /, -, SPACE
· Open bracket ‘(‘ and closed bracket ‘)’ must be in pairs
· If included, ‘+’ must be the first or second character (after a leading open bracket ‘(‘). For example:
· +1 650 123-4567
· (+1) 650 123-4567
· 1+ 650 123-4567 is not valid
Example
The following is an example of users in standard format.
[User] |
The following example shows how you can change the user mapping data of an existing user, user2. When you import the data, choose the option Overwrite Existing Data in the import tool.
The user user2 is mapped to the user ID ext_user2 in the system BCE, where BCE is the system alias of the system defined in the portal system landscape.
[User] |