立即与支持人员聊天
与支持团队交流

Defender 6.6 - Administration Guide

Getting started Managing Defender objects in Active Directory Configuring security tokens Securing VPN access Securing Web sites Securing Windows-based computers Defender Management Portal (Web interface) Securing PAM-enabled services Delegating Defender roles, tasks, and functions Automating administrative tasks Administrative templates Integration with Active Roles Push Notifications Appendices
Appendix A: Enabling diagnostic logging Appendix B: Troubleshooting common authentication issues Appendix C: Troubleshooting DIGIPASS token issues Appendix D: Defender classes and attributes in Active Directory Appendix E: Defender Event Log messages Appendix F: Defender Client SDK Appendix G: Defender Web Service API

Adding a license

To add a license

  1. On the computer where the Defender Administration Console is installed, open the Active Directory Users and Computers tool (dsa.msc).
  2. In the left pane (console tree), expand the appropriate domain node, and click to select the Defender container.
  3. On the menu bar, select Defender | License.
  4. On the License tab, click the Add License button.
  5. In the dialog box that opens, enter the license key provided to you by One Identity.
  6. Click OK.

Removing a license

You can remove licenses whose validity period has expired.

To remove a license

  1. On the computer where the Defender Administration Console is installed, open the Active Directory Users and Computers tool (dsa.msc).
  2. In the left pane (console tree), expand the appropriate domain node, and click to select the Defender container.
  3. On the menu bar, select Defender | License.
  4. In the Added licenses list, click to select the license you want to remove.
  5. Below the Added licenses list, click the Remove License button.

    When prompted, confirm that you want to remove the license.

Upgrading Licensing to new One identity branded version from release 6.6.0

Quest will provide a One Identity branded version of License Validator to One Identity. This version of LV can be used to generate and validate licenses for One Identity products only. It will not be backward compatible with the version of LV that Quest uses. It will use different (and unknown to Quest) private and public keys for license generation and validation, making the ability to read Quest generated licenses impossible, as well as making it impossible for Quest to validate newly created One Identity licenses.

LV has the concept of importing license files/keys. Defender implemented the LV with the concept of importing the Key only in latest release 6.6.0 and will continue to use in future release.

When upgrading to One Identity 6.6.0 from a previous version, the existing License Table will now include a new column titled "License" indicating whether the license is a QuestKey or OneIdentity license. After upgrading, you will need to contact the License Manager to obtain a new set of OneIdentity license keys to continue creating new or assigning Software Tokens.

If no OneIdentity license is loaded, the Defender Product will disable features related to creating, assigning, and programming new tokens. A warning message will also display, notifying you of a violation of the software transaction agreement. All QuestKey licenses will be deactivated, highlighted in red in the License Table, and will no longer be included in the total token and user count.

Managing Defender objects in Active Directory

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级