Add or edit a user in a self-hosted environment

For self-hosted installations, you first create users in your single sign-on environment, then manage their roles and permissions on the Oracle Empirica Signal Users page or the Edit Alternate Account page, depending on if the account is a principal account or an alternate account.

You can't add alternate accounts on the Add User screen.

Note:

This procedure does not apply for Oracle-hosted installations, unless you are a superuser. For more information, see Add and edit a user in an Oracle-hosted environment.

1. To use single sign-on for authentication in a self-hosted environment, create the user in your single sign-on application.
2. In the left navigation pane, click the Settings icon ().
3. In the Manage Users section, click Edit Users.
4. To add a user:
   1. Click Add a New User.
   2. Fill in the fields according to the table below.

      Field descriptions: Add or edit a primary or new user

      Field	Description
      Authentication	Authentication method.
      Username (Add User page only)	Unique name of the user account (up to 100 characters). You can reuse deleted user names. Does not apply if LDAP authentication is used. For more information, see Rename a user.
      First Name	First name of the user (up to 64 characters).
      Last Name	Last name of the user (up to 64 characters).
      Email	Email address of the user. This address (or addresses, separated by a comma) is used: As the default email address if the user chooses to be notified of data mining run completion notification. When a message is generated by a topic email notification rule. When you use the Send Message to All Users link on the Settings page. It is recommended that all users have an associated email address.
      User Profile	The user profile, or set of attributes (login group and quota), user roles, permissions, and default user preferences that can be applied to users. The default is specified on the Site Options page by making a selection from the Default User Profile drop-down list.
      Quota (Appears if you set the User Profile to None.)	Maximum amount of server space in megabytes (M) that the user is permitted to use for creating runs. If this limit is exceeded, the user cannot submit new runs (or re-runs). To indicate an unlimited amount of storage space, leave this field blank. If you enter 0, the user cannot create any runs even if the user has appropriate permissions.
      Login Group (Appears if you set the User Profile to None.)	Name of the login group to which the user belongs. Only a superuser can change the login group and will see a Change link. When a superuser selects the Change link, Oracle Empirica Signal asks for confirmation because Oracle discourages changing a user's login group. The superuser must click OK to enable the Login Group field.
      Password (Local authentication only)	Password for the user account (up to 64 characters). The password does not need to be unique. Note that users can also modify their own passwords. Follow any recommendations by your organization related to creating secure (hard-to-guess) passwords. You must create passwords according to the password restrictions set by your site administrator. Does not apply if LDAP or SSO authentication is used.
      Confirm Password (Local authentication only)	Re-enter the password for the user account to confirm it. Does not apply if LDAP or SSO authentication is used.
      Superuser	If selected, the user can perform any activity. This check box is available only if you are logged in as a superuser. If you are not a superuser, the label Superuser appears (without a check box) for any previously created superuser.
      Password never expires (Local authentication only)	If selected, the user password never expires. Note: If a user password has expired, a message at the top of the Edit User page tells you this when you edit the user. Does not apply if LDAP or SSO authentication is used.
      User must change password at next login (Local authentication only)	If selected, the user is required to change the password when next logging in. This option is cleared automatically once the user has changed the password. Does not apply if LDAP or SSO authentication is used.
      Account locked (Local authentication only)	If selected, the user cannot log in until you clear the check box. This check box is selected automatically for a user who tries to log in with an incorrect password more than the number of times allowed by the site option, Number of Attempts Allowed. Does not apply if LDAP or SSO authentication is used.
      Account disabled	If selected, the user account is disabled. Disabled users cannot log in, receive notifications, or have objects such as topics assigned to them. Note: When a local user password has expired, the user account becomes disabled. To allow the user to log in again, you must both assign a new password to the user and re-enable the user account.

5. To edit a user:
   1. Locate the user in the Users table.
   2. Click the Row Action menu () for the user, and then click Edit.
      • If the user is not an alternate account, the Edit User page appears.
      • If the user is an alternate account, the Edit Alternate Account appears.

      Note:

      You can edit only users in your login group.
   3. Fill in the according to the table above.
6. Click Save.
7. Use the links at the bottom of the Edit User page to provision newly created users with a user profile, roles, and permissions.

   Note:

   If you selected a user profile, the user is already provisioned with roles and permissions.

   If you are a superuser, you can also access the Manage Alternate Accounts page.

8. (Optional) Add or edit alternate accounts for this user using the Manage Alternate Accounts link.
9. (Optional) If you plan to use the Topics feature of Oracle Empirica Signal, do the following for newly created users:
   1. Add the user to one or more work teams.
   2. Assign work team permissions to the user.