Administrator Access Control

Overview

Oracle CPQ is commonly administered by teams of individuals who are responsible for administering different subsets of Oracle CPQ features. Administrator Access Control allows an Access Administrator to secure certain administrative features and prevent other Full Access users from accessing those pages, links and services.

Oracle CPQ has two methods to restrict access to Oracle CPQ administration features:

Administrator Groups is a new feature in Oracle CPQ 18B and replaces the Access Permissions feature when enabled.

Administrator Groups Available for release 18B and later*

Using Administrator Access Control with Administrator Groups, companies can delegate and restrict access to certain areas of CPQ’s setup and administration. This prevents unauthorized users from introducing unintentional errors, clarifies areas of responsibility, and protects sensitive or proprietary information.

When Administrator Groups are enabled and setup, Full Access users only have access to the administration pages and data to which they are entitled. To ensure this data is properly secured and the logged in user only sees links to the content they can access, Oracle has added a number of security features.

ClosedSecure Pages

The Admin Home page only displays the pages to which the logged in user has access. Members of the “All Access” group can access all pages and navigation menus. In the following example, the user has access to only a few of the administrative segments of the Admin Home page. The links are secured from unauthorized access.

Administration Platform


ClosedSecure Admin Drawer

When the Alta Navigation menu is enabled, Full Access users see an Admin Drawer in the upper left-hand corner of the screen under a "hamburger menu”. When the Administrator Access Control feature is turned on, the Admin Drawer only shows the pages to which the logged in user has access.

Secure Admin Drawer


ClosedSecure Navigation Menus

Administrators can customize the Navigation Menus for their users by providing links to internal and customized content. When these links point to administration features, they are removed when the user does not have access to the features. This security applies to headers, sub-headers, and sub-footers when using Top Navigation, Side Navigation, or Alta Navigation.

Secure navigation Menu

Customeize icons

If a custom link points to a restricted administrator page, it is not automatically hidden. An access denied message will display.

Restricted Admin page

Access denied


ClosedSecure SOAP Web Services

All SOAP APIs for administrative features that are public to Full Access users are secured, blocking unauthorized users from accessing data.

When using web services version 1.0 or version 2.0:

  • A SuperUser can access all administrator SOAP APIs (e.g. parts, groups, configuration, price books, data tables, users, exchange rates).
  • Authorized users can access designated administrator SOAP APIs.
  • Users trying to access restricted SOAP APIs will see an error message and the operation will fail.
  • The getGroups operation retrieves information for Sales groups only.
  • The modifyGroups operation can modify Sales groups only.

The following error displays in the response when a SOAP API to access data tables is called by an unauthorized user.

Sample SOAP API Error


ClosedSecure REST Web Services

All REST APIs for administrative features that are public to Full Access users are secured, blocking unauthorized users from accessing data.

  • A SuperUser can access all administrator REST APIs (e.g. parts, groups, configuration, price books, data tables, users, exchange rates).
  • Authorized users can access designated administrator REST APIs.
  • Users trying to access restricted REST APIs will see an error message and the operation will fail.

Sample REST API Error


Consider the following tips when using the Administrator Access Control feature:

  • Newly created Data Table folders and Product Families are only available to “All Access” users upon creation. An Access Administrator must grant access to those newly created items before they are usable by Full Access users who are not “All Access” users.
  • Bulk Data Services can only be globally allowed or restricted. A user with access to Bulk Data Services can access any data available for bulk upload or download, so grant access sparingly.
  • Users can only migrate settings when they have access to the features in both the target and the source site. If the user does not have access to a feature, the migration will fail.
  • Keep in mind that User Administrators can proxy login as any user. These users can bypass Access Controls by logging in as a Full Access user with greater access rights. As a result, grant User Administrator rights sparingly.

Access Permissions

When Administrator Groups are not enabled, all Host Company FullAccess users can view and edit all administrator modules by default (except users). Administrator Access Control is achieved using the Access Permissions feature that lets User Administrators restrict access to Product Families, Supported Product Families, and Data Table Folders for individual Full Access users.

If the user is restricted from accessing anything (even just one Product Family or one Data Table Folder), he/she will also not be able to access any other administrator modules (including Commerce, the Document Designer, Parts, and so on) through the Admin Home Page besides the Product Families, Supported Product Families, and Data Table Folders he/she explicitly has access to.

ClosedExample

For example, if FullAccess User 1 only has access to Product Family A, and is restricted from accessing all other Product Families, Supported Product Families, and Data Table Folders, the user will only be able to access Product Family A on the administrator side of the application. User 1 will have no access to any other administrator modules through the Admin Home Page, which will look like the screen shot below.

Administration Platform with restricted access

If FullAccess User 2 has not had access restricted to any Product Families, Supported Product Families, or Data Table Folders, he/she will have full access to all administrator modules (except users).


ClosedImportant Implementation Information

If you restrict access to any Product Families, Supported Product Families, or Data Table Folders, you also should modify the Navigation Menu  links so that the administrator(s) cannot access modules they should be restricted from through the Navigation Bar.

For example, in the image below, the user has had access restricted and cannot access any administrator modules besides Data Tables through the Admin Home Page, but the user can still access Users, Groups, Parts, Catalog Definition, and so on, through the Navigation Bar. Access to these links should be removed using Navigation Menus. For more information, see Navigation Menu.

Data Table Access only


Administration

Administrator Groups Available for release 18B and later*

ClosedEnable Administrator Groups for Your Site

ClosedAssign User Administrator Privileges to FullAccess Users

Users with User Administrator permissions see all users when they click on the users tab. In addition, User Administrators can perform the following functions:

  • Proxy in as other users
  • Modify users
  • Reset passwords
  • Add new users or inactivate existing users
  • Create shared folders
  • Commerce archiving if the user belongs to Host Company
  • Schedule Usage Reports if the user belongs to Host Company
  • Access the Migration Center (Oracle CPQ 21B and later)
  • Send Broadcast Emails (Oracle CPQ 21B and later)
  • Access Single Sign-On (SSO) (Oracle CPQ 21B and later)

When the Enable Administrator Groups option on the General Site Options page is set to Yes, an Access Administrator checkbox displays as a Permissions property on the User Administration and My Profile pages.

To assign User Administrator privileges to FullAccess users, perform the following steps:

  1. Open the Admin Home page.
  2. Under Users, select Internal Users.

    The User Administration List page opens.

  3. Click the user login link for the FullAccess user you want to make an Access Administrator.

    The User Administration page opens.

  4. Select the User Administrator checkbox.

    User Administration

  5. Click Apply.

Note: Users must be logged in as a SuperUser or a FullAccess user with Access Administrator permissions in order to change the Access Administrator permission for other users.

ClosedUpdate User Permissions Using SOAP Web Services



ClosedAssign Access Administrator Privileges to FullAccess Users

Available for release 18B and later*

When the Enable Administrator Groups option on the General Site Options page is set to Yes, an Access Administrator checkbox displays as a Permissions property on the User Administration and My Profile pages.

Notes:

  • Only Access Administrators can create and edit Administrator groups.
  • This checkbox is always checked for the Host Company SuperUser and defaults to unchecked for all FullAccess users.
  • When Administrator Groups are first enabled, the SuperUser must assign Access Administrator permissions to other FullAccess users.

To assign Access Administrator privileges to FullAccess users, perform the following steps:

  1. Open the Admin Home page.
  2. Under Users, select Internal Users.

    The User Administration List page opens.

  3. Click the user login link for the FullAccess user you want to make an Access Administrator.

    The User Administration page opens.

  4. Select the Access Administrator checkbox.

    User Administration

  5. Click Apply.

Note: Users must be logged in as a SuperUser or a FullAccess user with Access Administrator permissions in order to change the Access Administrator permission for other users.


ClosedAssign Allow Proxy Login Privileges

Proxy login allows administrators to log in as another user to verify changes to their setup or isolate issues reported by users. When the Enable Administrator Groups option on the General Site Options page is set to Yes, an Allow Proxy Login checkbox displays as a Permissions property on the User Administration and My Profile pages.

To grant Allow Proxy Login privileges to FullAccess users, perform the following steps:

  1. Open the Admin Home page.
  2. Under Users, select Internal Users.

    The User Administration List page opens.

  3. Click the user login link for the FullAccess user you want to make an Access Administrator.

    The User Administration page opens.

  4. Select the Allow Proxy Login checkbox.

    User Administration

  5. Click Apply.

Note: Users must be logged in as a SuperUser or a FullAccess user with Access Administrator permissions to change the Allow Proxy Login permission.


ClosedAssign Web Services Access and SSO Settings

When the Web Services Only checkbox is selected for an internal user, that user may only make Web Services calls to the Oracle CPQ site; logging in through the web interface will not be permitted. Only FullAccess users with the ability to create/modify users can change this setting.

  • Any user that does not have Web Services Only checked will have their password expire within the defined Admin setting. The user will be prompted to change their password on next login.
  • Users with ‘Web Services Only checked do not have their password expire, due to the nature of the account.

To assign Web Services access and SSO Settings, perform the following steps:

  1. Open the Admin Home page.
  2. Under Users, select Internal Users.

    The User Administration List page opens.

  3. Click the user login link for the FullAccess user you want to make an Access Administrator.

    The User Administration page opens.

    User Administration

  4. Select the Web Services Only checkbox to only a user to access an Oracle CPQ site via Web Services calls.

    When selected, the user can only access the system by logging in through the SOAP or REST APIs. The user will not be able to access the Oracle CPQ user interface. For more information on Oracle CPQ Web Services see the topics An Overview of Web Services 2.0 and SOAP APIs and REST API Overview topics.

  5. Select the Enable SSO setting.

    If the User is enabled for Single Sign-On login and the site is enabled for SSO, the user can access login via this method.

  6. Set the External SSO ID, if desired.

    If the External SSO ID is set it will be used for SSO, otherwise the User's Login will be used.

  7. Click Apply.

ClosedView Groups Based on Group Type

ClosedCreate and Edit Administrator Groups

ClosedAdd Users to Administrator Groups from the User Administration Page

Access Permissions

ClosedSet Administrator Access Permissions when Administrator Groups are Disabled

  1. Log in as the SuperUser or a FullAccess user with permission to create and modify users.
  2. ClosedNavigate to the User Administration page.

    1. Click Admin to go to the Admin Home Page.
    2. Click Internal Users in the Users section.

      The User Administration List page opens.

  3. Set Access Permissions for a FullAccess user without User Administrator access.

    • Only administrators with Access Administrator privileges can grant Access Administrator privileges to other Full Access users.
    • There is a maximum of 500 FullAccess users per site.
    1. Click the name of a FullAccess user that does not have permission to create and modify users.
      That user’s User Administration page opens.

    2. Click the Access Permissions tab.
    3. Select/deselect the Product Families, Supported Product Families, and Data Table Folders that the user should/should not have access to, respectively.

      If the Has Access checkbox is selected for any component, the user will have access to view and modify that component on the admin side.

      User Administration

  4. Click Apply or Update to save changes to the user’s admin access permissions.

Notes

The User List shows all users. If the logged in user is not a User Administrator they will be able to see other user's detail pages in read-only mode. They can edit their own details by clicking their login in this list or by opening their My Profile page from the navigation bar or header. To restrict access to the Users list create an Admin Group which excludes access to that feature.

Admin Access Control does not impact the user side. A FullAccess user who is restricted from a Product Family on the admin side can still interact with the Product Family on the user side, unless access to the Product Family is restricted for that user through the Home Page. For more information, see the topic Home Page.

Related Topics

Related Topics Link IconSee Also