Oracle Transportation Management Users

New Oracle Transportation and Global Trade Management Cloud user accounts must be provisioned within Oracle Transportation and Global Trade Management Cloud User Manager as well as in the Single Sign-On solution. The Oracle Transportation Management service requires a user record to be defined within the service for a user to be able to perform anything within the service. Every Oracle Transportation Management user also requires a password within the service even though this password may never be used by the end user. When provisioning service users, it is recommended to provide a strong password for this user regardless. This password is required internally within the service but also for possible Inbound Integration use.

Note: Application User Passwords Restrictions: Note that there are now longer forbidden characters that cannot be used for any service users' passwords by default. All characters can now be used in passwords for any service users. The ALLOW RESTRICTED PASSWORD CHARACTERS Optional Feature has been promoted and is no longer available.

The Oracle Transportation Management service user record contains numerous attribute fields for the defining and controlling the user. There are attributes which control authentication capability like Effective Date and Expiration Date. Some of these fields like First Name, Last Name and Email Address are purely informational. There are fields that are set internally from the application after successful login like the Last Login Data. And there are specific business use fields like Document Use Profile and Approval Rule Profile. The Account Policy field controls the account Policy assigned to the user.

In order to successfully login to the Oracle Transportation Management Cloud Service through Federated Single Sign-On, Single Sign-On (SSO) or OAuth2, you must provide a Nickname on the user record in the Oracle Transportation Management service. The Nickname is the key field which links a user to the Single Sign-On solution. In the case of an interactive end user, this Nickname field must be mapped to the end user’s email address that you will define in the Single Sign-On solution. While for an OAuth 2 user, this Nickname field will be mapped to the Client ID of a configured Confidential Application. These nicknames must be unique per cloud service instance, and this is enforced by a check that is performed during user creation and modification. These nicknames are also case-insensitive so there is no way for two different Oracle Transportation Management service users to have different case nicknames.

Note: Every Oracle Transportation Management user requires a password within the service even though this password may never be used by the end user. It is recommended to provide a strong password for every user.

When provisioning users, it is necessary to specify the correct domain. By default, users created in one domain will only have access to PUBLIC data and data defined in their domain.

The User manager is accessed via Configuration and Administration > User Management > User Manager. For more details see the "Manage User" help topic.

Oracle Transportation Management User Manager User Interface

To create or update an Oracle Transportation and Global Trade Management Cloud user via the User Manager screens, perform the following steps:

Log in as a DBA.ADMIN user as another Admin user of the user's domain.
Navigate to Configuration and Administration > User Management > User Manager.
Using the finders, search for the user needing updating.
Click on the user link to edit the user record.
Modify what is required.
Click on Finished to save the user change.