This scenario demonstrates how to use the Synchronize Functions wizard in iSeries™ Navigator to propagate a single signon configuration across multiple systems in a mixed OS/400® release environment. Administrators can save time by configuring single signon once and propagating that configuration to all of their systems, instead of configuring each system individually.
You are a network administrator for a large auto parts manufacturer. You manage five systems with iSeries Navigator. One system operates as the central system, which stores data and manages the endpoint systems. You have read about the benefits of single signon and you want to configure a single signon environment for your enterprise. You have just completed the process of setting up a test environment on one system and you want to extend your single signon environment throughout the enterprise. You have four other servers to configure and you want to find a way to configure them as efficiently as possible.
You know that iSeries Navigator provides the Synchronize Functions wizard that allows you to copy the single signon configuration from one system and apply it to other i5/OS® V5R3 or later systems. This eliminates the need to configure each system separately.
However, one of your systems runs OS/400® Version 5 Release 2 (V5R2). OS/400 V5R2 does not support the Synchronize Functions wizard, which means that separately configure this system to match the current network authentication service and EIM configurations on your model system.
This scenario has the following advantages:
As the network administrator for MyCo, Inc., you want to create a single signon environment for your enterprise in which all your servers will participate and you want to configure your servers as quickly and easily as possible.
The objectives of this scenario are as follows:
Refer to Domains to learn how two types of domains, an EIM domain and a Windows® 2000 domain, both fit into the single signon environment.
The following figure illustrates the network environment for this scenario.
The figure illustrates the following points relevant to this scenario.
Windows 2000 server
System MC1 - Central system
System A - Model system
The model system should be configured similarly to the system identified as System A in the Scenario: Creating a single signon test environment scenario. Refer to this scenario to ensure that all of the single signon configuration tasks on the model system are completed and verified.
System B
System C
System D
Administrator's PC
Only required for PC used to administer network authentication service.
Successful implementation of this scenario requires that the following assumptions and prerequisites are met:
System MC1 - Central system prerequisites
To verify that these licensed programs have been installed, complete the following:
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.
System A - Model system prerequisites
This scenario assumes that System A is properly configured for single signon. Refer to the Scenario: Creating a single signon test environment scenario to ensure that all of the single signon configuration tasks on the model system are completed and verified.
To verify that these licensed programs have been installed, complete the following:
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.
System B, System C, and System D - Endpoint systems prerequisites
To verify that these licensed programs have been installed, complete the following:
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.
Windows 2000 server prerequisites
To propagate the network authentication service and EIM configurations from the model system, System A to the endpoint systems, System B and System C, complete the following tasks:
You need to understand the concepts related to single signon, which include network authentication service and Enterprise Identity Mapping (EIM) concepts, before you implement this scenario. See the following information to learn about the terms and concepts related to single signon: