If you decide to map assets to users during the import, you have to ensure that each asset can unambiguously be mapped to an existing user. So to import assets, it is required that a user with the same name already exists in the INETAPP. The import does not create new users.
Users can be real persons or dummy users, such as "storage". The mapping is done with the username
which is always unique. The username in INETAPP refers to the Login ID of the user. You can create your own Login IDs in the Users and Groups Manager if required - or, if you are using the User Import, then imported user accounts will have the login type "Windows Authentication" and the corresponding Windows ID as their login ID.
The mapping of the username
in the external data source and the username
in the INETAPP can be achieved in the following two ways:
If you're using a database connection, you can select a separate data source - table or query - to import the connected users from. To make this work, it is required to have a matching identifier in the table that contains the assets and in the table containing the users:
<ASSET TABLE NAME>
that will be used to map the user data to another database table.<USER TABLE NAME>
that can be mapped with the referencing table name.<USER TABLE NAME>
that contains the username, which will be set on the asset.Note: You can still only use one database connection. Both sources, for assets and for users, must reside in the same connection.
If you're using an LDAP connection, you can select a separate data class to import the connected users from. The prerequisites are the same, as above:
<ASSET OBJECT CLASS>
that will be used to map the user data to another object class.<USER OBJECT CLASS>
that can be mapped with the referencing object class.<USER OBJECT CLASS>
that contains the username, which will be set on the asset.Note: You can still only use one LDAP connection. Both source object classes, for assets and for users, must reside in the same connection.