View this scenario to learn how to configure your Management Central servers to participate in a single signon environment. After administrators complete the scenario for propagating a single signon configuration across multiple systems, they can do the necessary configuration so that their Management Central servers can participate in the single signon environment.
You are a system administrator for a medium-sized parts manufacturer. You have been using the iSeries™ Navigator Management Central server to manage a central server and three endpoint servers for the last three years. Your responsibilities include applying PTFs, creating new users on the network and other administrative duties. You have always liked having the ability to send and install PTFs to multiple systems from your central server; this saves you time. Your company has just upgraded to V5R4, and your company's security administrator has implemented a new security policy for your company, which requires user passwords to be different on each system in the network. Previously, the Management Central servers required that user profiles and passwords be identical across the network. You've learned that in i5/OS® V5R4 that if you enable the Management Central servers for single signon, you no longer need to have matching user profiles and passwords on each endpoint system to use the Management Central server's functions. This limits the need to manage passwords on your i5/OS systems.
You completed the Scenario: Enable single signon for i5/OS for one of your new systems, and then you completed the Scenario: Propagate network authentication service and EIM across multiple systems. Now you want to want to configure all of your Management Central servers to participate in this single signon environment.
This scenario has the following advantages:
You are one of three system administrators that work for your company. You and the other two administrators, Amanda and George, want to create a small single signon environment that decreases your administrative expense and simplifies your access to centrally managed applications and network assets.
The objectives of this scenario are as follows:
The following figure illustrates the network environment for this scenario:
The figure illustrates the following points relevant to this scenario.
The model system should be configured similarly to the system identified as System A in the Scenario: Create a single signon test environment. Refer to this scenario to ensure that all of the single signon configuration tasks on the model system are completed and verified.
Only required for PC used to administer network authentication service.
Successful implementation of this scenario requires that the following assumptions and prerequisites are met:
This scenario assumes that the central system is properly configured for single signon. Refer to the Scenario: Create a single signon test environment to ensure that all of the single signon configuration tasks on the central system are completed and verified.
When you propagate network configuration service configuration among servers, sensitive information like passwords are sent across the network. You should use SSL to protect this information, especially if it is being sent outside your Local Area Network (LAN). See Scenario: Secure all connections to your Management Central server with SSL for details.
When you propagate network configuration service configuration among servers, sensitive information like passwords are sent across the network. You should use SSL to protect this information, especially if it is being sent outside your Local Area Network (LAN). See Scenario: Secure all connections to your Management Central server with SSL for details.
To enable single signon for users of the Management Central servers, complete the following tasks: