Completing the installation
Regardless of whether you are installing Delegated Admin in a Unix or Linux or Windows environment, perform the relevant steps in this section after you complete the previous OS-specific tasks.
Navigate to the type of installation you want to complete for the relevant steps.
|
The PingDirectoryProxy server
Before you begin
|
The following task assumes that when you ran the |
About this task
If you are installing Delegated Admin on the PingDirectoryProxy server, you must configure the proxy instance using the delegated-admin-for-proxy.dsconfig script as described in Locations other than PingDirectoryProxy.
To configure all instances of the PingDirectory server:
Steps
-
Apply the commands from the
delegated-admin.dsconfigbatch file to all instances of the PingDirectory server.$ ./bin/dsconfig \ --bindDN "cn=Directory Manager" \ --bindPassword <password> \ --no-prompt \ --batch-file webapps/delegator/delegated-admin.dsconfig \ --applyChangeTo server-group -
Apply the commands from the
delegated-admin.dsconfigbatch file to all instances of the PingDirectory server, as explained in Replicated instances of PingDirectory.
Replicated instances of the PingDirectory server
About this task
If you are installing Delegated Admin on one or more replicated instances of the PingDirectory server:
Steps
-
Apply the following commands in
delegated-admin.dsconfigto each instance:$ ./bin/dsconfig \ --bindDN "cn=Directory Manager" \ --bindPassword <password> \ --no-prompt \ --batch-file webapps/delegator/delegated-admin.dsconfig \ --applyChangeTo server-group
External web server
Before you begin
|
The following steps assume that when you ran the |
Steps
-
Open
config.jsin a text editor. -
Change the variable values to specify the location of the PingDirectory server.
config.jsVariable Value window.DS_HOSTHost name of the PingDirectory server
window.DS_PORTHTTPS port of the PingDirectory server
To view an example outline that features these settings, see
example.config.js. -
Save your changes to
config.js. -
Create a CORS policy for the Delegated Admin HTTP servlet extension, where <origin> represents the public name of the host, proxy, or load balancer that presents the Delegated Admin web application.
Example:
dsconfig create-http-servlet-cross-origin-policy --policy-name "Delegated Admin Cross-Origin Policy" --set "cors-allowed-methods: GET" --set "cors-allowed-methods: OPTIONS" --set "cors-allowed-methods: POST" --set "cors-allowed-methods: DELETE" --set "cors-allowed-methods: PATCH" --set "cors-allowed-origins: <origin>" dsconfig set-http-servlet-extension-prop --extension-name "Delegated Admin" --set "cross-origin-policy:Delegated Admin Cross-Origin Policy"
-
(Optional) If you will be enabling administrators to run Delegated Admin reports in your configuration, run
dsconfigwith theset-http-servlet-cross-origin-policy-propoption.Example:
dsconfig set-http-servlet-cross-origin-policy-prop \ --policy-name "Delegated Admin Cross-Origin Policy" \ --set cors-exposed-headers:Content-Disposition
All locations except the PingDirectoryProxy server
About this task
To continue installing Delegated Admin on a PingDirectory server or on an external web server:
Steps
-
Run the following command with
delegated-admin.dsconfigon the appropriate server:$ ./bin/dsconfig \ --bindDN "cn=Directory Manager" \ --bindPassword <password> \ --no-prompt \ --batch-file webapps/delegator/delegated-admin.dsconfig
Next steps
|
You can’t sign on to Delegated Admin until you configure the rights of the delegated administrators. Learn more about configuring administrative rights, the REST resource type, session timeout values, and other properties in Configuring Delegated Admin. |
After you configure Delegated Admin, verify that the application is installed and working successfully.