Contact information for LDAP user accounts
Enter the data used by this user account for contacting the identity by telephone.
Table 27: Contact data
|
Image |
Picture to display in a telephone book, for example.
|
|
Email address |
Email address. If you assigned an account definition, the email address is made up of the identity’s default email address depending on the manage level of the user account. |
|
Phone |
Telephone number. If you have assigned an account definition, the input field is automatically filled out with respect to the manage level. |
|
Mobile phone |
Mobile number. If you have assigned an account definition, the input field is automatically filled out with respect to the manage level. |
|
Pager |
Pager number. |
|
Fax |
Fax number. If you have assigned an account definition, the input field is automatically filled out with respect to the manage level. |
|
Phone private |
Private telephone number. |
|
Phone, private (2) |
Extra telephone number. |
|
International ISDN no. |
International ISDN number. |
|
Additional email addresses |
Additional email addresses. |
|
X.121 address |
Addressing as X.121 address. |
|
X.400 address |
Address in X.400 format. |
Address information for LDAP user accounts
Enter the following address data used by this user account for contacting the identity.
Table 28: Address data
|
Room |
Room. If you have assigned an account definition, the input field is automatically filled out with respect to the manage level. |
|
Registered address |
Postal address. |
|
Address |
Postal address. |
|
Address (private) |
Postal address (private). |
|
Mailbox |
Mailbox. If you have assigned an account definition, the input field is automatically filled out with respect to the manage level. |
|
Street |
Street or road. If you have assigned an account definition, the input field is automatically filled out with respect to the manage level. |
|
Zip code |
Zip code. If you have assigned an account definition, the input field is automatically filled out with respect to the manage level. |
|
State |
State. If you have assigned an account definition, the input field is automatically filled out with respect to the manage level. |
Organizational data for LDAP user accounts
Enter the following organizational main data.
Table 29: Organizational main data
|
Business unit |
Business unit to which the identity is assigned. |
|
Department |
Identity's department If you have assigned an account definition, the input field is automatically filled out with respect to the manage level. |
|
Location |
Identity's location. If you have assigned an account definition, the input field is automatically filled out with respect to the manage level. |
|
Location ID |
Location ID (country and city). |
|
Employment |
Job details. |
|
Personnel number |
Number for identifying the identity, in addition to their ID. |
|
Title |
The user’s academic title. If you have assigned an account definition, the input field is automatically filled out with respect to the manage level. |
|
Organizational position |
Details of position in the company, for example, directory, or department manager. |
|
Office |
Office. If you have assigned an account definition, the input field is automatically filled out with respect to the manage level. |
|
Preferred language |
Preferred language. If you have assigned an account definition, the input field is automatically filled out with respect to the manage level. |
|
Account manager |
Manager responsible for the user account. |
|
Secretary |
Secretary’s user account. |
|
Country ID |
The country ID. |
|
Company |
Identity's company. If you have assigned an account definition, the input field is automatically filled out with respect to the manage level. |
|
Car license plate |
Vehicle's license plate. |
EduPerson extensions for LDAP user accounts
On the Higher education tab, the following information for the eduPerson object class is displayed.
Table 30: eduPerson main data
| User identifier |
A unique identifier for an identity. The identifier should be have the form "user@scope". The user part is a name-based identifier for the identity. The scope part is the administrative domain of the identity system in which the identifier was created and assigned. |
| Unique alias |
Unique and permanent pseudonymous identifier of an identity. This value is provider-specific. |
| Global identifier |
Unique, globally valid identifier for an identity. |
| Nickname |
The short name of the identity. |
| Institution |
Distinguished name of the institution to which the identity belongs. |
| Institution units |
Distinguished name of the unit in the institution to which the identity belongs. You can enter more that one unit. |
| Institution unit (primary) |
Distinguished name of the primary unit in the institution to which the identity belongs. |
| Affiliation |
Categorization of the identity's affiliation with the institution, such as student, faculty, staff, alumni. You can enter more that one type. |
| Scoped affiliation |
Category and institution to which the identity belongs. You can enter more that one scoped affiliation.
Example: student@university.com |
| Primary affiliation |
Primary category and institution to which the identity belongs.
Example: student@university.com |
| Permissions |
Permissions that control access and how certain resources are accessed. |
| ORCID IDs |
Unique identifiers used primarily to relate an identity to its scientific publications. |
| Level of assurance |
Quantifies the trustworthiness of the identity. |
| Prior user identifier |
Previous user IDs that were associated with the identity. The values must not contain the currently valid user identifier. |
| Analytics tag |
String that can be used for reporting or analysis. |
Related topics
button.
.