To simplify administration, Crystal Enterprise supports LDAP authentication for user and group accounts. Before users can use their LDAP user name and password to log on to Crystal Enterprise, you need to map their LDAP account to Crystal Enterprise. When you map an LDAP account, you can choose to create a new Crystal Enterprise account or link to an existing Crystal Enterprise account.
Before setting up and enabling LDAP authentication, ensure that you have your LDAP directory set up. For more information, refer to your LDAP documentation.
The LDAP Configuration Wizard will lead you through the setup of LDAP authentication, step by step.
Repeat this step to add more than one LDAP host of the same server type if you want to add hosts that can act as failover servers. If you want to remove a host, highlight the host name and click Delete. For more information on multiple hosts, refer to Managing multiple LDAP hosts.
By default, each supported server type's server attribute mappings and search attributes are already set.
If your LDAP Server allows anonymous binding, leave this area blankCrystal Enterprise servers and clients will bind to the primary host via anonymous logon.
Although groups can be mapped from multiple hosts, only one set of referral credentials can be set. Therefore if you have multiple referral hosts, you must create a user account on each host that uses the same distinguished name and password.
If this field is set to zero, no referrals will be followed.
This is the lowest security option. Before Crystal Enterprise can establish an SSL connection with the LDAP host (to authenticate LDAP users and groups), it must receive a security certificate from the LDAP host. Crystal Enterprise does not verify the certificate it receives.
This is a medium security option. Before Crystal Enterprise can establish an SSL connection with the LDAP host (to authenticate LDAP users and groups), it must receive and verify a security certificate sent to it by the LDAP host. To verify the certificate, Crystal Enterprise must find the Certificate Authority that issued the certificate in its certificate database.
Tip: Java applications (such as the Java version of the Crystal Enterprise web desktop) always use this option, regardless of the setting you choose.
This is the highest security option. Before Crystal Enterprise can establish an SSL connection with the LDAP host (to authenticate LDAP users and groups), it must receive and verify a security certificate sent to it by the LDAP host. To verify the certificate, Crystal Enterprise must find the Certificate Authority that issued the certificate in its certificate database. It must also be able to confirm that the CN attribute on the server certificate exactly matches the host name of the LDAP host as you typed it in the "Add LDAP host" field in the first step of the wizard. That is, if you entered the LDAP host name as ABALONE.rd.crystald.net:389, using CN =ABALONE:389 in the certificate would not work.
Tip: The host name on the server security certificate is the name of the primary LDAP host. Therefore if you select this option you cannot use a failover LDAP host.
Type the host name of each machine in the SSL Host box, and then click Add.
The settings for the default host are used:
New Alias Options allow you to specify how LDAP aliases are mapped to Enterprise accounts. Select either:
Use this option when you know users have an existing Enterprise account with the same name; that is, LDAP aliases will be assigned to existing users (auto alias creation is turned on). Users who do not have an existing Enterprise account, or who do not have the same name in their Enterprise and LDAP account, are added as new LDAP users.
Use this option when you want to create a new account for each user. If the user has already created an account through the sign
Use this option to automatically create a new alias for every LDAP user mapped to Crystal Enterprise. New LDAP accounts are added for users without Crystal Enterprise accounts, or for all users if you selected the "Create a new account for every added LDAP alias" option.
Use this option when the LDAP directory you are mapping contains many users, but only a few of them will use Crystal Enterprise. Crystal Enterprise does not automatically create aliases and Enterprise accounts for all users. Instead, it creates aliases (and accounts, if required) only for users who log on to Crystal Enterprise.
New user accounts are configured to use named user licenses. Named user licenses are associated with specific users and allow people to access the system based on their user name and password. This provides named users with access to the system regardless of how many other people are connected. You must have a named user license available for each user account created using this option.
New user accounts are configured to use concurrent user licenses. Concurrent licenses specify the number of people who can connect to Crystal Enterprise at the same time. This type of licensing is very flexible because a small concurrent license can support a large user base. For example, depending on how often and how long users access Crystal Enterprise, a 100 user concurrent license could support 250, 500, or 700 users.
Crystal Decisions http://www.crystaldecisions.com/ Support services http://support.crystaldecisions.com/ |