The Dos and Don'ts for Using the Security Console

The Security Console is a powerful tool, but you don't need all of its power for your initial setup. Here's an overview of the Security Console tabs and their uses. Only setup users, or other users with the IT Security Manager job role, can access the Security Console.

Tab	Dos and Don'ts
Roles	Create your own roles as described in Securing Sales and Service guide.
Users	Don't create users or provision job roles here. For sales, you must create users as resources using the Manage Users task, resource import, and REST web services. Follow the instructions in the rest of this guide to create users and provision job roles. If you do create user accounts in the Security Console, then you must create the users again as resources using the Manage Users task and link the accounts you created in the Create Users page. Use this tab only to manage user passwords and update user email addresses. Note that all users, even members of the sales organization who can't access the Security Console, can reset their own passwords. That's done by clicking the user name in the welcome page and selecting the Preferences option from the Settings and Actions menu. While you can use this tab to change user names, doing so requires some extra setup for Oracle BI Answers, the embedded reporting tool for building and modifying reports. Oracle BI Answers creates a separate GUID from the user ID when you create a user. If you change the user ID, then you must update the BI Answers GUID by running the Rename Accounts Self-Service utility. You can download the utility from My Oracle Support, article Oracle Fusion BI: Self Service Forget Accounts and Rename Accounts Tools (Doc ID 2635720.1).
Analytics	Review role assignments and compare roles. This advanced security functionality is covered in the Securing Sales and Service guide.
Certificates	The sales application doesn't use this functionality.
User Categories	Specify password policies and manage notifications users receive about their accounts and passwords. You can specify different behavior for different categories of users. For the sales application, all the users you create are initially assigned to the Default category. But you can create additional user categories and move users to them.
Single Sign-On	Configure single sign-on.
API Authentication	Used for defining JSON Web Tokens other applications can use to validate themselves with Oracle CX Sales and Fusion Service.
Administration	Use to set role copying preferences and other advanced features covered in the Securing Sales and Service guide.

You can find information about more advanced tasks, including security configuration, in the Securing Sales and Service and the Extending Sales and Service guides.