SYSUSER Account

The installation of Oracle Utilities Operational Device Management supplies an initial account SYSUSER, by default. This account is defined by default in the default security realm in the provided templates, is provided as the initial User object in the authorization model and is used as the default user in some transactions.

You cannot physically remove SYSUSER account as it is used by the initial installation and owned by Oracle Utilities Operational Device Management, but it can be disabled under the following conditions:

• Alternative identities have been configured for the authentication and authorization components of the product.

• Every facility in the implementation that uses the SYSUSER account as the default identity has been changed to an alternative to prevent misconfiguration of the facility.

Note: Oracle recommends that you use the appropriate alternatives for transactions instead of the SYSUSER account.

The following facilities use SYSUSER as the default identity, if used:

Facility	Comments
Default User in Message Option	This is used for XAI and MPL (older releases only).
HTTP Login User context type on Message Sender	Used for Utilities P2P integrations. Ensure HTTP User Password is also set correctly for alternative.
WEB_IWS_SUPER_USERS in ENVIRON.INI file	Used for supporting IWS user proxy connections
WEB_IWS_MDB_RUNAS_USER in ENVIRON.INI file	Used to support user proxy connections in Message Driven Bus.
Batch Controls	Replace SYSUSER as the user used for submission of any batch controls in batch control configuration files, batch edit configuration files or in the Oracle Scheduler configuration.

You can deactivate the SYSUSER account by:

• Removing SYSUSER from configured security realm for authentication, preventing the user from authenticating.

• Setting the User Enable attribute (SYSUSER User object) to Disable, deactivating the account from any unauthorized activity in Oracle Utilities Operational Device Management.