Users

Oracle WMS Cloud includes a built-in authentication mechanism where users can be setup with their own user-id and passwords to access the Oracle Warehouse Management (WMS) Web UI and Mobile RF application. In addition, it also supports authenticating users against external identity providers (IDP). It supports multiple authentication mechanisms:

• SAML2 based Single Sign On, or SSO in short - A web-based authentication standard that can be used only to login to the WMS Web UI.
• OAuth2 - Another authentication standard that can be used for the WMS Web UI and Mobile RF.

Note: Application User Password Restrictions

• Password should be at least 6 Characters long.

• Password cannot be all alphabetic or all numeric.

• Please note that there are forbidden characters that cannot be used for any users' passwords. The following "#", "[","]", “!”, “@”, “$” characters cannot be used in passwords for any users. Special characters cannot be used.

• Password will never be used if integrated with external IDP.

• Company level password policy can override ‘user password’ policy.

• ‘User Password’ can be configured within the Oracle Warehouse Management Service Web UI in Company Security Configuration.

The Oracle WMS Cloud Service user record contains numerous attribute fields for defining and controlling users. There are attributes that control authentication capability like Effective Date and Expiration Date. Some of these fields like First Name, Last Name, and Email Addresses are purely informational. There are fields that are set internally from the application after successful login like default printers.

In order to successfully login to the Oracle WMS Cloud Service through Federated Single Sign-On, Single Sign-On (SSO) or OAuth2, you must provide an alternate user on the user record in the Oracle Warehouse Management service. The alternate user is the key field which links a user to the Single Sign-On solution. These logins are also case-sensitive.

Note: Every Oracle Warehouse Management user requires a password within the service. It is recommended to provide a strong password for every user. Although, Oracle WMS Cloud provides a maximum password lifecycle of 365 days, users should change passwords frequently as a best practice. Application Administrators should use their organizations password rotation policy. The created password must be changed and updated once before the password life cycle ends to ensure the account accessibility.

When provisioning users, it is necessary to specify the correct company/facility. By default, users created in one company/facility will only have access to data defined in their own company/facility. The Oracle WMS Cloud service has and requires different user roles that are utilized within the application. Permissions to access data for different user roles are as follows:

Administrator User Role – Permissions

Category	Permissions
Company / Facility	Add, Delete, and Change Company; Add, Delete, and Change Facility;
User	Add, Delete,and Change User
Group	Add, Delete, and Change Group
Menu	Modify Menu, Save Company Menu, Save Group Menu
Columns	Modify View Columns, Reorder View Columns
View	Save Company View, Save Group View, Save User View

Note: By default, Administrators have access to all companies that the facility is eligible for.

Management User Role – Permissions

Category	Permissions
Facility	Add, Delete, and Change Facility;
User	Add and Change User
Menu	Modify Menu, Save Group Menu
Columns	Modify View Columns, Reorder View Columns
View	Save Group View, Save User View

Supervisor User Role – Permissions

Category	Permissions
Facility	Change Facility
User	Change User
Menu	Modify Menu, Save Group Menu
Columns	Modify View Columns, Reorder View Columns
View	Save Group View, Save User View

Guard User Role – Permissions

• Read-only access. Users cannot create, copy, edit or delete.

Employee User Role – Permissions

• Read-only access. Users cannot create, copy, edit or delete.

Support User

In some instances, it is necessary to view log files as the Oracle WMS Cloud (WMS) support team is assisting with any existing issues. To initiate this process, customers need to create a support user in WMS. Once a customer creates a support user, the support team will have access to log files and other tools required to analyze customer issues.

Note: The Create Support User option is available only if the customer selects a user that is not currently a support user (refer to support user column). The reason is that the selected user serves as a template for the support user that is about to be created and it cannot be an existing support user’s template. As soon as any issues triaged with the support user are resolved, customers can disable the support user. If you do not delete the support user, the system will automatically disable the support user cannot be reactivated at this point life in days is reached, and the support user cannot be reactivated at this point.