DOCSLIB.ORG

Opentext Documentum D2 (Version 16.4) Installation Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

OpenText ™ Documentum ™ D2 Version 16.4 Installation Guide Legal Notice This documentation has been created for software version 16.4. It is also valid for subsequent software versions as long as no new document version is shipped with the product or is published at https://knowledge.opentext.com. Open Text Corporation 275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1 Tel: +1-519-888-7111 Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440 Fax: +1-519-888-0677 Support: https://support.opentext.com For more information, visit https://www.opentext.com Copyright © 2018 Open Text. All Rights Reserved. Trademarks owned by Open Text. Adobe and Adobe PDF Library are trademarks or registered trademarks of Adobe Systems Inc. in the U.S. and other countries. One or more patents may cover this product. For more information, please visit, https://www.opentext.com/patents Disclaimer No Warranties and Limitation of Liability Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However, Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the accuracy of this publication. Table of Contents Preface ................................................................................................................................. 7 Chapter 1 Getting Started ............................................................................................. 9 Know Before You Start....................................................................................... 9 Preparing for Installation ................................................................................... 9 Instructions for Installing D2 ............................................................................. 10 Understanding the D2 Keystore Utility .............................................................. 12 Running the D2 Keystore Utility........................................................................ 13 Registering D2 DFC Clients as Privileged Clients................................................ 15 Chapter 2 Upgrading D2 .............................................................................................. 17 Planning Your D2 Upgrades.............................................................................. 17 Running the D2 Migration Utility ...................................................................... 18 Upgrading D2 4.6 to D2 16.4 on the Documentum Server .................................... 21 Re-running the Upgrade Utility......................................................................... 24 Upgrading D2 on the Web Application Server .................................................... 25 Removing Lockbox Artifacts ............................................................................. 26 Chapter 3 Installing D2 on the Documentum Server .................................................... 29 Installing D2 on the Documentum Server ........................................................... 29 Chapter 4 Deploying D2 DAR Files Manually ............................................................... 33 Deploying D2 DAR Files Manually.................................................................... 33 Chapter 5 Installing D2 on the Web Application Server ............................................... 35 Limitations of D2 Core Installer......................................................................... 35 Installing D2 on Apache Tomcat for Microsoft Windows ..................................... 35 Installing D2 on Apache Tomcat for a Linux Environment................................... 36 Installing D2 on IBM WebSphere ....................................................................... 37 Installing D2 on Oracle WebLogic...................................................................... 39 Installing D2 on Redhat JBOSS .......................................................................... 40 Installing D2 on VMware vFabric tcServer for Microsoft Windows ...................... 41 Installing D2 REST Extension Framework .......................................................... 42 Configuring D2 REST Extension Framework ...................................................... 43 Chapter 6 Deploying D2 in a Docker Environment ....................................................... 45 Preparing the D2 Docker Environment............................................................... 45 Running the D2 Docker Containers.................................................................... 45 Add Webapp as DFC Privileged Client .............................................................. 45 3 Table of Contents Chapter 7 Configuring D2 ............................................................................................ 47 Installation Validation....................................................................................... 47 Configuring D2 Config...................................................................................... 54 Configuring D2 Client....................................................................................... 57 Configuring D2 Java Method Server................................................................... 68 File Transfer Modes .......................................................................................... 68 Installing DCM Browser Extension (Internet Explorer)........................................ 69 Installing DCM Browser Extension (Firefox)....................................................... 69 Installing DCM Browser Extension (Chrome) ..................................................... 70 Installing DCM Browser Extension (Safari)......................................................... 70 Uninstalling Documentum Client Manager Browser Extensions .......................... 71 Uninstalling Documentum Client Manager Native Application ........................... 71 Configuring File Transfer Modes ....................................................................... 72 Configuring logback.xml for the Documentum Server......................................... 74 Removing Debug Logs from the JBoss 7.1.1 JMS Log........................................... 75 Configuring Documentum Server server.ini ....................................................... 75 Configuring D2 Auditing .................................................................................. 76 Configuring Application Server Pooling Session ................................................. 76 Configuring Compatibility with Documentum Information Rights Management (IRM)........................................................................................... 76 Configuring the D2EventSenderMailMethod...................................................... 77 Configuring D2 to use CTS for Fast Web-Enabled C2 Renditions.......................... 77 Enabling POP3S Mail Configuration .................................................................. 78 Chapter 8 Best Practices ............................................................................................. 81 Enabling Compression at the Application Server when using Apache Tomcat or JBoss ................................................................................................ 81 Optimizing Performance for Widgets and Large Numbers of Content.................. 81 Improving Content Transfer Performance .......................................................... 82 General Tuning Tips ......................................................................................... 83 Chapter 9 Configuring Authentication ......................................................................... 85 Single Sign On (SSO) Authentication for D2 ....................................................... 85 Configuring Microsoft Windows NT Unified Logon (NTLM) .............................. 85 Configuring Kerberos ....................................................................................... 86 Configuring Kerberos for Multiple Domains...................................................... 88 Configuring TrustedReverseProxy for Various SSO Environments ....................... 89 Adding Administrator Credentials to the D2 keystore for SSO............................. 91 Configuring the Shiro.ini file for Interoperability with D2-Config and the Documentum Method Server....................................................................... 92 Configuring the shiro.ini file for Custom SSO Integrations .................................. 92 Configuring Security Assertion Markup Language (SAML) Support.................... 93 Chapter 10 Installing Advanced Publishing Services .................................................... 97 Advanced Publishing Services Plug-in ............................................................... 97 4 Table of Contents Deploying Advanced Publishing Services Automatically .................................... 97 Installing the Advanced Publishing Services Plug-in ....................................... 98 Installing Advanced Publishing Services Libraries on a Linux Environment ................................................................................................ 99 Installing Advanced Publishing Services Libraries on Microsoft Windows ................................................................................................... 100 Installing D2–Link .....................................................................................
Recommended publications
  • Unified, Easy-To-Manage Endpoint Security

    Unified, Easy-To-Manage Endpoint Security

    Unified, Easy-to-Manage Endpoint Security Microsoft® Forefront™ Protect Business Continuity with Improved Management Client Security protects of Endpoint Security laptops, desktops, and file The release of the next generation of on Windows firewall activities. The agent servers with integrated Forefront client security protects business incorporates proven technologies already protection against laptops, desktops, and file servers against in use on millions of computers worldwide malware. It simplifies viruses, spyware, rootkits, and other and is backed by efficient and effective control of endpoint malware. The solution includes: threat response from the Microsoft security and provides n A single agent that provides antivirus Malware Protection Center. better visibility into the and antispyware protection, vulnerability Forefront Client Security is designed to overall protection of the assessment and remediation, and host simplify administration and save valuable environment. Defenses firewall management. time through its single management are easily managed from n A central management server that console and policy configuration, the Microsoft Forefront enables administrators to configure, central update infrastructure, and Management Console update, and report on agent activity automated endpoint discovery. It also code-named “Stirling.” across the enterprise. integrates with existing investments in Microsoft technologies. The two components work together to www.microsoft.com/ provide unmatched visibility and control To reduce risk,
  • Impact 360 Content Producer Installation and Upgrade Guide 5

    Impact 360 Content Producer Installation and Upgrade Guide 5

    Content Producer Installation and Upgrade Guide Version 11.1 Document Revision 1.00 Confidential and Proprietary Information of Verint Systems Inc. 11/540,185; US 11/540,320; US 11/540,900; US 11/540,902; © 1992–2012 Verint Systems Inc. All Rights Reserved Worldwide. US 11/567,808; US 11/567,852; US 11/583,381; US Confidential and Proprietary Information of Verint Systems Inc. 11/608,340; US 11/608,350; US 11/608,358; US 11/616,490; US 11/621,134; US 11/691,530; US 11/692,983; US All materials (regardless of form and including, without 11/693,828; US 11/693,923; US 11/693,933; US 11/712,933; US 11/723,010; US 11/742,733; US 11/752,458; US limitation, software applications, documentation, and any other 11/776,659; US 11/824,980; US 11/831,250; US 11/831,257; information relating to Verint Systems, its products or services) are the exclusive property of Verint Systems Inc. Only expressly US 11/831,260; US 11/831,634; US 11/844,759; US 11/872,575; US 11/924,201; US 11/937,553; US 11/959,650; authorized individuals under obligations of confidentiality are US 11/968,428; US 12/015,375; US 12/015,621; US permitted to review materials in this document. By reviewing these materials, you agree to not disclose these materials to any 12/053,788; US 12/055,102; US 12/057,442; US 12/057,476; US 12/107,976; US 12/118,789; US 12/118,792; US third party unless expressly authorized by Verint Systems, and 12/164,480; US 12/245,781; US 12/326,205; US 12/351,370; to protect the materials as confidential and trade secret information.
  • Administrator's Guide

    Administrator's Guide

    Trend Micro Incorporated reserves the right to make changes to this document and to the product described herein without notice. Before installing and using the product, review the readme files, release notes, and/or the latest version of the applicable documentation, which are available from the Trend Micro website at: http://docs.trendmicro.com/en-us/enterprise/scanmail-for-microsoft- exchange.aspx Trend Micro, the Trend Micro t-ball logo, Apex Central, eManager, and ScanMail are trademarks or registered trademarks of Trend Micro Incorporated. All other product or company names may be trademarks or registered trademarks of their owners. Copyright © 2020. Trend Micro Incorporated. All rights reserved. Document Part No.: SMEM149028/200709 Release Date: November 2020 Protected by U.S. Patent No.: 5,951,698 This documentation introduces the main features of the product and/or provides installation instructions for a production environment. Read through the documentation before installing or using the product. Detailed information about how to use specific features within the product may be available at the Trend Micro Online Help Center and/or the Trend Micro Knowledge Base. Trend Micro always seeks to improve its documentation. If you have questions, comments, or suggestions about this or any Trend Micro document, please contact us at [email protected]. Evaluate this documentation on the following site: https://www.trendmicro.com/download/documentation/rating.asp Privacy and Personal Data Collection Disclosure Certain features available in Trend Micro products collect and send feedback regarding product usage and detection information to Trend Micro. Some of this data is considered personal in certain jurisdictions and under certain regulations.
  • User Manual TREK-722/723

    User Manual TREK-722/723

    User Manual TREK-722/723 RISC All-In-One Mobile Data Terminal Copyright The documentation and the software included with this product are copyrighted 2012 by Advantech Co., Ltd. All rights are reserved. Advantech Co., Ltd. reserves the right to make improvements in the products described in this manual at any time without notice. No part of this manual may be reproduced, copied, translated or transmitted in any form or by any means without the prior written permission of Advantech Co., Ltd. Information provided in this manual is intended to be accurate and reliable. How- ever, Advantech Co., Ltd. assumes no responsibility for its use, nor for any infringe- ments of the rights of third parties, which may result from its use. Acknowledgements TI and AM37x are trademarks of Texas Instruments.. Microsoft Windows is registered trademarks of Microsoft Corp. All other product names or trademarks are properties of their respective owners. Product Warranty (2 years) Advantech warrants to you, the original purchaser, that each of its products will be free from defects in materials and workmanship for two years from the date of pur- chase. This warranty does not apply to any products which have been repaired or altered by persons other than repair personnel authorized by Advantech, or which have been subject to misuse, abuse, accident or improper installation. Advantech assumes no liability under the terms of this warranty as a consequence of such events. Because of Advantech’s high quality-control standards and rigorous testing, most of our customers never need to use our repair service. If an Advantech product is defec- tive, it will be repaired or replaced at no charge during the warranty period.
  • HTTP Client API for Jscript

    HTTP Client API for Jscript

    HTTP Client API for JScript Version 9.7 April 2015 This document applies to HTTP Client API for JScript Version 9.7. Specifications contained herein are subject to change and these changes will be reported in subsequent release notes or new editions. Copyright © 1999-2015 Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors. The name Software AG and all Software AG product names are either trademarks or registered trademarks of Software AG and/or Software AG USA, Inc. and/or its subsidiaries and/or its affiliates and/or their licensors. Other company and product names mentioned herein may be trademarks of their respective owners. Detailed information on trademarks and patents owned by Software AG and/or its subsidiaries is located at http://softwareag.com/licenses. Use of this software is subject to adherence to Software AG's licensing conditions and terms. These terms are part of the product documentation, located at http://softwareag.com/licenses/ and/or in the root installation directory of the licensed product(s). This software may include portions of third-party products. For third-party copyright notices, license terms, additional rights or re- strictions, please refer to "License Texts, Copyright Notices and Disclaimers of Third-Party Products". For certain specific third-party license restrictions, please refer to section E of the Legal Notices available under "License Terms and Conditions for Use of Software AG Products / Copyright and Trademark Notices of Software AG Products". These documents are part of the product documentation, located at http://softwareag.com/licenses and/or in the root installation directory of the licensed product(s).
  • (12) United States Patent (10) Patent No.: US 7,921.461 B1 Golchikov Et Al

    (12) United States Patent (10) Patent No.: US 7,921.461 B1 Golchikov Et Al

    USOO7921461B1 (12) United States Patent (10) Patent No.: US 7,921.461 B1 Golchikov et al. (45) Date of Patent: Apr. 5, 2011 (54) SYSTEMAND METHOD FOR ROOTKIT S.8. 53 A. : SS Eyrdseter . et. al.. ............... 7 1. DETECTION AND CURE 2004/O181561 A1 9, 2004 Knox et al. 2005, 0021994 A1 1/2005 Barton et al. (75) Inventors: Andrey V. Golchikov, Moscow (RU); 2005/0278788 A1 12/2005. Jindal et al. Andrey V. Sobko, Moscow (RU) 2006/0031673 A1 2/2006 Becket al. .................... T13, 164 2006.0053270 A1* 3, 2006 Dunn et al. 712/13 (73) Assignee: Kaspersky Lab, ZAO, Moscow (RU) 2.99. A. : 29: RSU ca.tal. ... 2. (*) Notice: Subject to any disclaimer, the term of this 2008.0034429 A1 ck 2/2008 Schneider ....................... T26/23 patent is extended or adjusted under 35 OTHER PUBLICATIONS U.S.C. 154(b) by 1115 days. Simon Baker et al. "Checking Microsoft Windows(R) Systems for (21) Appl. No.: 11/623,364 Signs of Compromise', Oct. 28, 2005, version 1.3.4, pp. 1-18.* y x- - - 9 * cited by examiner (22) Filed: Jan. 16, 2007 Primary Examiner — Farid Homayoumehr (51) Int. Cl. Assistant Examiner — Michael Guirguis ge. 5.b4. 3:08: (74) Attorney, Agent, or Firm — Bardmesser Law Group GSB 23/00 (2006.01) (57) ABSTRACT (52) U.S. Cl. ................... 726/23: 726/24; 726/25; 713/2 ASVstem. method and computer program product for SVStem (58) Field of Classification Search .................... 726/26, ystem, computer program pr ySt. 726/23 25: 713/2 for detecting a rootkit on a computer having an operating S lication file f let h his s system, including a native application in ring 0 which, when ee appl1cauon Ille Ior complete searcn n1Story.
  • Groove Gfs Browser Helper Grooveshellextensions.Dll

    Groove Gfs Browser Helper Grooveshellextensions.Dll

    Groove gfs browser helper grooveshellextensions.dll Continue Equipment Info maakt gebruik van biscuits Equipment Information onderdeel van DPG Media. Onze sites en applications gebruiken cookies, JavaScript en vergelijkbare technologie onder andere om je een optimale gebruikerservaring te bieden. Ook kunnen we hierdoor het gedrag van bezoekers vastleggen en analyseren, en deze informatie toevoegen aan bezoekersprofielen. Biscuits kunnen worden gebruikt om Op Equipment Advertising information those Tonen en artikelen aan te bevelen die aansluiten op je interesses. Ook derden kunnen je internetgedrag volgen, zoals bijvoorbeeld het geval - is a bij built-in video van YouTube. Biscuits kunnen gebruikt worden om op sites van derden relevantenties te tonen. Dankzij cookies van derde partijen kun je daarnaast informatie delen via social media, zoals Twitter en Facebook. Meer informatie hierover vind je op hardware.info/extra/cookies. Om pagina's op Hardware Info te kunnen bekijken, moet je de cookies accepteren door op 'Ja, ik accepteer cookies' te klikken. The original GrooveShellExtensions.dll file is a software component of Microsoft Office 2007 at Microsoft. GrooveShellExtensions.dll is an addition to Microsoft Browser Helper Object (BHO) for Microsoft Internet Explorer. Known as Groove Folder Sync, this allowed Office 2007 users to access Groove files in the IE web browser window and helped synchronize updated files. It included a contextual menu. His location was C: Files of the Microsoft Office-Office12-GrooveShellExtensions.dll. No reference to Office14 or above can be found, indicating that it has not been installed since Office 2010 or later. The Groove in Office 2007 product allows users to collaborate by sharing workspaces synchronized through relay servers with any other user they're invited to join the workspace.
  • ERNW Newsletter 31 / June 2010 Secure Configuration of Microsoft

    ERNW Newsletter 31 / June 2010 Secure Configuration of Microsoft

    ERNW Newsletter 31 / June 2010 Dear Partners, dear Colleagues, Welcome to the 31th edition of the ERNW Newsletter with the title: Secure Configuration of Microsoft Internet Explorer, Version 8 Version 1.0, 11th of June 2010 By: Enno Rey ([email protected]) Christopher Werny ([email protected]) Oliver Röschke ([email protected]) Abstract This newsletter evaluates configuration options, reflecting security and possible usability impact, incorporating typical large scale enterprise usage of browser based content. The evaluation was done for a globally operating enterprise. Note We provide some supporting files, namely: some regfiles containing the settings we recommended for the given environment. Use at your own risk and only if you fully understand the impact! an XLS with the recommended settings, based on the Microsoft XLS doc on GPO settings. miscellaneous stuff, e.g. an XLS with some documentation on potentially needed CLSIDs. A ZIP file with these can be found at http://www.ernw.de/download/ernw_nl_31_ie8config_supporting_docs.zip Disclaimer: the recommended settings are deployed in a sufficiently large global network. So they "work in production". Still, your mileage might vary. Please use the stuff cautiously. Any use is at your own risk. Definition – Umsetzung – Kontrolle 1 1 INTRODUCTION ............................................................................................. 5 1.1 Project Goals ............................................................................................................ 5 1.2 Technical goals ........................................................................................................
  • Building Anti-Phishing Browser Plug-Ins: an Experience Report

    Building Anti-Phishing Browser Plug-Ins: an Experience Report

    Building Anti-Phishing Browser Plug-Ins: An Experience Report Thomas Raffetseder, Engin Kirda, and Christopher Kruegel Secure Systems Lab, Technical University of Vienna {tr,ek,chris}@seclab.tuwien.ac.at Abstract stolen. These credentials are typically used to login into the online banking web site and to transfer money to the at- Phishing is an online identity theft that aims to steal tacker’s bank account. Although phishing is a simple social sensitive information such as user names, passwords, and engineeringattack, it has provento be surprisingly effective. credit card numbers. Although phishing is a simple social Hence, the number of phishing scams is continuing to grow, engineering attack, it has proven to be surprisingly effec- and the costs of the resulting damages is increasing. For tive. Hence, the number of phishing scams is continuing example, the Anti-Phishing Working Group received over to grow, and the costs of the resulting damages is increas- 35,000 unique phishing reports in November 2006, com- ing. Researchers as well as the IT industry have identified pared to around 7,000 in November of the year before [2]. the urgent need for anti-phishing solutions and recently, a Figure 1 shows a phishing email that targets the cus- number of solutions to mitigate phishing attacks have been tomers of a U.S. bank. The attackers have imitated the look proposed. Several of these approaches are browser plug- and feel of the Bank of America online banking web site ins. with the aim of fooling users into believing that the mail In 2005, we implemented a Firefox anti-phishing is authentic.
  • Security Analysis of Browser Extension Concepts

    Security Analysis of Browser Extension Concepts

    Saarland University Faculty of Natural Sciences and Technology I Department of Computer Science Bachelor's thesis Security Analysis of Browser Extension Concepts A comparison of Internet Explorer 9, Safari 5, Firefox 8, and Chrome 14 submitted by Karsten Knuth submitted January 14, 2012 Supervisor Prof. Dr. Michael Backes Advisors Raphael Reischuk Sebastian Gerling Reviewers Prof. Dr. Michael Backes Dr. Matteo Maffei Statement in Lieu of an Oath I hereby confirm that I have written this thesis on my own and that I have not used any other media or materials than the ones referred to in this thesis. Saarbr¨ucken, January 14, 2012 Karsten Knuth Declaration of Consent I agree to make both versions of my thesis (with a passing grade) accessible to the public by having them added to the library of the Computer Science Department. Saarbr¨ucken, January 14, 2012 Karsten Knuth Acknowledgments First of all, I thank Professor Dr. Michael Backes for giving me the chance to write my bachelor's thesis at the Information Security & Cryptography chair. During the making of this thesis I have gotten a deeper look in a topic which I hope to be given the chance to follow up in my upcoming academic career. Furthermore, I thank my advisors Raphael Reischuk, Sebastian Gerling, and Philipp von Styp-Rekowsky for supporting me with words and deeds during the making of this thesis. In particular, I thank the first two for bearing with me since the release of my topic. My thanks also go to Lara Schneider and Michael Zeidler for offering me helpful advice.
  • Protecting Browsers from Extension Vulnerabilities

    Protecting Browsers from Extension Vulnerabilities

    Protecting Browsers from Extension Vulnerabilities Adam Barth Adrienne Porter Felt Prateek Saxena Aaron Boodman Electrical Engineering and Computer Sciences University of California at Berkeley Technical Report No. UCB/EECS-2009-185 http://www.eecs.berkeley.edu/Pubs/TechRpts/2009/EECS-2009-185.html December 18, 2009 Copyright © 2009, by the author(s). All rights reserved. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission. Acknowledgement We would like to thank Nick Baum, Erik Kay, Collin Jackson, Matt Perry, Dawn Song, David Wagner, and the Google Chrome Team. This work is partially supported by the Air Force Office of Scientific Research under MURI Grant No. 22178970-4170. Protecting Browsers from Extension Vulnerabilities Adam Barth, Adrienne Porter Felt, Prateek Saxena Aaron Boodman University of California, Berkeley Google, Inc. fabarth, afelt, [email protected] [email protected] Abstract browser’s full privileges. If an attacker can exploit an ex- tension vulnerability, the attacker can usurp the extension’s Browser extensions are remarkably popular, with one in broad privileges and install malware on the user’s machine. three Firefox users running at least one extension. Although At this year’s DEFCON, Liverani and Freeman presented well-intentioned, extension developers are often not security attacks against a number of popular Firefox extensions [23].
  • Netiq Securelogin 8.5 Service Pack 3 Release Notes September 2017

    Netiq Securelogin 8.5 Service Pack 3 Release Notes September 2017

    NetIQ SecureLogin 8.5 Service Pack 3 Release Notes September 2017 NetIQ SecureLogin 8.5 Service Pack 3 (SP3) enhances the product capability and resolves several previous issues. Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the NetIQ SecureLogin forum on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources. The documentation for this product and the latest Release Notes are available on the NetIQ website in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click comment on this topic at the bottom of any page in the HTML version of the documentation posted at the NetIQ SecureLogin documentation page. To download this product, see the NetIQ Downloads website. Section 1, “What’s New?,” on page 1 Section 2, “System Requirements,” on page 3 Section 3, “Installing or Upgrading,” on page 3 Section 4, “Known Issues,” on page 3 Section 5, “Legal Notices,” on page 5 1 What’s New? This release includes the following: Section 1.1, “Software Fixes,” on page 1 1.1 Software Fixes This release includes the following software fixes: Section 1.1.1, “Smart Card Pin Auto-fill Does Not Work For Second Application,” on page 2 Section 1.1.2, “Performance Issue During Smart Card Pin Auto-fill While Using .Net Applications,”