Arquitectura ISOPOS utilizando al convertidor de puente completo con fase desplazada

To create a protected virtual directory

1 Make a copy of the appropriate eapps_virdirs batch file provided in the SWSE logical profile directory.

The eapps_virdirs batch files are used to create Siebel virtual directories. For additional

information on creating custom virtual directories, see Siebel Installation Guide for the operating system you are using.

2 Edit the copied eapps_virdirs file to specify the name and other details of the virtual directory you want to create for the Siebel application.

For example, enter p_eservice as a virtual directory name for Siebel eService.

3 Run the eapps_virdirs batch file, and a Siebel virtual directory with the name you specified is created.

It is recommended that you save the edited eapps_virdirs file so that it can be used if you need to restore or migrate your virtual directory environments.

4 Set the Authentication setting for the virtual directory you created to Windows Authentication as follows:

a In the Internet Service Manager explorer, right-click the virtual directory you created in the previous steps, then choose Properties.

The Properties dialog box appears.

b Click the Directory Security tab.

c Click Edit in the Anonymous Access and Authentication Control section.

d The Authentication Methods dialog box appears.

e Check the Integrated Windows Authentication check box, and uncheck all others. Make sure that the Allow Anonymous Access box is unchecked.

NOTE: On some versions of the IIS Web Server, an Integrated Authentication check box is not displayed. In this case, make sure that the Allow Anonymous Access box is unchecked and enable Windows Authentication.

f Click Yes on the Internet Service Manager caution dialog, and then click OK when you return to the Authentication Methods dialog box.

The Directory Security tab in the Properties dialog box appears.

g Click Apply, and then click OK.

Creating Users in the Directory (Windows Integrated Authentication)

To implement Web SSO using Windows Integrated Authentication, you must create users in the Active Directory, as described in this topic.

Web Single Sign-On Authentication _■ Process of Implementing Windows Integrated Authentication

Create three users in the Active Directory, using values similar to those shown in Table 18 on page 189. The attribute names, sAMAccountName and Password, are suggestions; your entries might vary depending on how you make attribute assignments in “Setting Up Active Directory to Store Siebel User Credentials for Windows Integrated Authentication” on page 186. Complete other attribute fields for each user, as needed.

The database account for all users is the same, and must match the database account reserved for externally-authenticated users described in “Setting Up Active Directory to Store Siebel User

Credentials for Windows Integrated Authentication” on page 186. P represents the password in that database account. For information about formatting the database account attribute entry, see

“Requirements for the LDAP Directory or Active Directory” on page 114.

NOTE: Make sure the application user has privileges to search and write to all records in the directory.

Table 18. Active Directory Records

User sAMAccountName Password Database Account

Anonymous

user ■ Enter the user ID of the anonymous user record for the Siebel application you are implementing.

You can use a seed data anonymous user record, as described in “Seed Data” on page 387, for a Siebel customer or partner application. For example, for Siebel eService, enter GUESTCST.

■ You can create a new user record or adapt a seed anonymous user record for a Siebel employee application.

APPUSER or a name of your choice. APPUSERPW or a password of your choice.

A database account is not used for the application user.

A test user TESTUSER or a name of your choice. TESTPW or a password of your choice.

username=LDAPUSER password=P.

Web Single Sign-On Authentication _■ Process of Implementing Windows Integrated Authentication

This task is a step in “Process of Implementing Windows Integrated Authentication” on page 184.

For purposes of confirming connectivity to the database, you can use the following procedure to add the test user for any Siebel application. However, if you are configuring a Siebel employee or partner application, and you want the user to be an employee or partner user, complete with position, division, and organization, then see the instructions for adding such users in “Internal Administration of Users” on page 245.

To add user records to the database

1 Log in as an administrator to a Siebel employee application, such as Siebel Call Center.

2 Navigate to the Administration - User screen, then the Users view.

3 In the Users list, create a new record.

4 Complete the following fields for the test user, then save the record. Use the indicated guidelines.

Suggested entries are for this example. You can complete other fields, but they are not required.

5 Verify that the seed data user record exists for anonymous users of the Siebel application you implement. For example, verify that the seed data user record with user ID GUESTCST exists if you are implementing Siebel eService. If the record is not present, then create it using the field values in Table 48 on page 388. You can complete other fields, but they are not required.

This record must also match the anonymous user you create in “Creating Users in the Directory (Windows Integrated Authentication)” on page 188. You can adapt a seed data anonymous user or create a new anonymous user for a Siebel employee application.

Field Guideline

Last Name Required. Enter any name.

First Name Required. Enter any name.

User ID For example, TESTUSER

Required. This entry must match the sAMAccountName attribute value for the test user in the directory. If you used another attribute instead of sAMAccountName, then it must match that value.

Responsibility Required. Enter the seed data responsibility provided for registered users of the Siebel application that you implement. For example, enter Web Registered User for Siebel eService. If an appropriate seed responsibility does not exist, such as for a Siebel employee

application, then assign an appropriate responsibility that you create.

New Responsibility Optional. Enter the seed data responsibility provided for registered users of the Siebel application that you implement. For example, enter Web Registered User for Siebel eService. This responsibility is automatically assigned to new users created by this test user.

Web Single Sign-On Authentication _■ Process of Implementing Windows Integrated Authentication

Setting Web Single Sign-On Authentication Parameters