Oracle Cloud Infrastructure Documentation

Integrate with Database User Management (MSSQL)

Prerequisites

Before you install and configure a Database User Management (Microsoft SQL Server) orchestrated system, you should consider the following pre-requisites and tasks.

Certified Components

The Microsoft SQL Server system can be any one of the following:
  • Microsoft SQL Server 2005, 2008, 2012, 2014, 2016, 2019

Supported Modes

Database User Management (Microsoft SQL Server) orchestrated system supports Managed System mode.

Supported System Operations

The Database User Management (Microsoft SQL Server) orchestrated system supports the following Microsoft SQL Server operations:
  • Create UserName
  • Create UserLogin
  • Change UserLogin password
  • Delete UserLogin
  • Assign Roles to a userName
  • Revoke Roles from a userName

Create a System User Account for Database User Management (MSSQL) System Operations

  1. Verify the following requirements for your Microsoft SQL Server installation before configuring the orchestrated system.
    • The Microsoft SQL Server TCP/IP port is enabled. The default port is 1433.
      To enable the TCP/IP port:
      1. Open the Microsoft SQL Server Configuration Manager.
      2. Click SQL Server Network Configuration.
      3. Click Protocols for MSSQLSERVER.
      4. In the right frame, right-click TCP/IP and then click Enable.
    • Mixed mode authentication is enabled.
    • The TCP/IP port is not blocked by a firewall.
  2. Create Login using the following query:
    Create LOGIN serviceuser with PASSWORD='password' , DEFAULT_DATABASE =DBname
GO
  3. Create a user using the following query:
    USE DBname;
Create USER serviceuser with LOGIN serviceuser;
GO
  4. Assign the following permissions and roles to the created user:
    ALTER ROLE db_datawriter ADD MEMBER serviceuser;
ALTER ROLE db_datareader ADD MEMBER serviceuser;
ALTER ROLE db_accessadmin ADD MEMBER serviceuser;
ALTER ROLE db_owner ADD MEMBER serviceuser;
exec sp_addsrvrolemember 'serviceuser', 'securityadmin';

Configure

You can establish a connection between Microsoft SQL Server and Oracle Access Governance by entering connection details. To achieve this, use the Orchestrated Systems functionality available in the Oracle Access Governance Console.

Navigate to the Orchestrated Systems Page

Navigate to the Orchestrated Systems page of the Oracle Access Governance Console, by following these steps:
  1. From the Oracle Access Governance navigation menu  icon Navigation menu, select Service Administration → Orchestrated Systems .
  2. Select the Add an orchestrated system button to start the workflow.

Select system

On the Select system step of the workflow, you can specify which type of system you would like to onboard.

  1. Select Database User Management (MSSQL).
  2. Click Next.

Enter details

On the Add Details step of the workflow, enter the details for the orchestrated system:
  1. Enter a name for the system you want to connect to in the Name field.
  2. Enter a description for the system in the Description field.
  3. Decide if this orchestrated system is an authoritative source, and if Oracle Access Governance can manage permissions by setting the following check boxes.
    • This is the authoritative source for my identities

      Select one of the following:

      • Source of identities and their attributes: System acts as a source identities and associated attributes. New identities are created through this option .
      • Source of identity attributes only: System ingests additional identity attributes details and apply to existing identities. This option doesn't ingest or creates new identity records.
    • I want to manage permissions for this system
    The default value in each case is Unselected.
  4. Select Next.

Add Owner

You can associate resource ownership by adding primary and additional owners. This drives self-service as these owners can then manage (read, update or delete) the resources that they own. By default, the resource creator is designated as the resource owner. You can assign one primary owner and up to 20 additional owners for the resources.
Note

When setting up the first Orchestrated System for your service instance, you can assign owners only after you enable the identities from the Manage Identities section.
To add owners:
  1. Select an Oracle Access Governance active user as the primary owner in the Who is the primary owner? field.
  2. Select one or more additional owners in the Who else owns it? list. You can add up to 20 additional owners for the resource.
You can view the Primary Owner in the list. All the owners can view and manage the resources that they own.

Account settings

On the Account settings step of the workflow, enter how you want Oracle Access Governance to manage accounts when the system is configured as a managed system:
  1. When a permission is requested and the account doesn't already exist, select this option to create new accounts . This option is selected by default. When selected, Oracle Access Governance creates an account if one doesn't exist when a permission is requested. If you clear this option, permissions are provisioned only for existing accounts in the orchestrated system. If no account exists, the provisioning operation fails.
  2. Select the recipients for notification emails when an account is created. The default recipient is User. If no recipients are selected, notifications aren't sent when accounts are created.
    • User
    • User manager
  3. Configure Existing Accounts
    Note

    You can only set these configurations if allowed by the system administrator. When global account termination settings are enabled, application administrators can't manage account termination settings at the orchestrated-system level.
    1. Select what to do with accounts when early termination begins: Choose the action to perform when an early termination begins. This happens when you need to revoke identity accesses before official termination date.
      • Delete: Deletes all accounts and permissions managed by Oracle Access Governance.
        Note

        If specific orchestrated system doesn't support the action, no action is taken.
      • Disable: Disables all accounts and disables permissions managed by Oracle Access Governance.
        • Delete the permissions for disabled accounts: To ensure zero residual access, select this to delete directly assigned permissions and policy-granted permissions during account disablement.
      • No action: No action is taken when an identity is flagged for early termination by Oracle Access Governance.
    2. Select what to do with accounts on the termination date: Select the action to perform during official termination. This happens when you need to revoke identity accesses on the official termination date.
      • Delete: Deletes all accounts and permissions managed by Oracle Access Governance.
        Note

        If specific orchestrated system doesn't support Delete action, then no action is taken.
      • Disable: Disables all accounts and disables permissions managed by Oracle Access Governance.
        • Delete the permissions for disabled accounts: To ensure zero residual access, select this to delete directly assigned permissions and policy-granted permissions during account disablement.
        Note

        If specific orchestrated system doesn't support the Disable action, then account is deleted.
      • No action: No action is taken on accounts and permissions by Oracle Access Governance.
  4. When an identity leaves your enterprise you must remove access to their accounts.
    Note

    You can only set these configurations if allowed by your system administrator. When global account termination settings are enabled, application administrators cannot manage account termination settings at the orchestrated-system level.

    Select one of the following actions for the account:

    • Delete: Delete all accounts and permissions managed by Oracle Access Governance.
    • Disable: Disable all accounts and mark permissions as inactive.
      • Delete the permissions for disabled accounts: Delete directly assigned and policy-granted permissions during account disablement to ensure zero residual access.
    • No action: Take no action when an identity leaves the organization.
    Note

    These actions are available only if supported by the orchestrated system type. For example, if Delete is not supported, you will only see the Disable and No action options.
  5. When all permissions for an account are removed, for example when an identity moves between departments, you may need to decide what to do with the account. Select one of the following actions, if supported by the orchestrated system type:
    • Delete
    • Disable
    • No action
  6. Manage accounts that aren't created by Access Governance: Select to manage accounts that are created directly in the orchestrated system. With this, you can reconcile existing accounts and manage them from Oracle Access Governance.
Note

If you don't configure the system as a managed system then this step in the workflow will display but is not enabled. In this case you proceed directly to the Integration settings step of the workflow.
Note

If your orchestrated system requires dynamic schema discovery, as with the Generic REST and Database Application Tables integrations, then only the notification email destination can be set (User, Usermanager) when creating the orchestrated system. You cannot set the disable/delete rules for movers and leavers. To do this you need to create the orchestrated system, and then update the account settings as described in Configure Orchestrated System Account Settings.

Integration settings

On the Integration settings step of the workflow, enter the configuration details required to allow Oracle Access Governance to connect to the Microsoft SQL Server.

  1. In the Easy connect URL for the database field, enter an easy connect URL to connect to the Microsoft SQL Server database, using the following syntax jdbc:sqlserver://[host]:[port];[databaseName];[encrypt];[trustServerCertificate]. For further information, consult the JDBC driver documentation..
  2. In the Username field, enter the administration username you will use to connect to the Microsoft SQL Server database.
  3. Enter the password for the adminstration user in the Password/Confirm password fields.
  4. In the Connection properties field, enter any connection properties that will be used to configure a secure connection. They should be key value pairs in the following format: key1=val1#key2=val2.
  5. The agent for this orchestrated system requires a Microsoft SQL Server driver jar in the classpath. Details of how this is used by the agent can be found in Custom Jar Support. The Microsoft SQL Server jar name and checksum should be in the format of <jarName>::<jarChecksum>.
  6. Update Database inclusion list with one or more database names that data should be included in the dataload.
  7. Update Database exclusion list with one or more database names that data should be excluded from the dataload.
  8. Click Add to create the orchestrated system.

Finish up

On the Finish Up step of the workflow, you are asked to download the agent you will use to interface between Oracle Access Governance and Microsoft SQL Server database. Select the Download link to download the agent zip file to the environment in which the agent will run.

After downloading the agent, follow the instructions explained in the Agent Administration article.

Finally, you are given a choice whether to further configure your orchestrated system before running a data load, or accept the default configuration and initiate a data load. Select one from:
  • Customize before enabling the system for data loads
  • Activate and prepare the data load with the provided defaults

Post Configuration

There are no post configuration steps associated with a Microsoft SQL Server system.