Support for Sending User ID on Attach when AP_SAME SpecifiedLast reviewed: July 31, 1997Article ID: Q135316 |
The information in this article applies to:
SUMMARYIn response to customer requests, Microsoft created an update for SNA Server that allows APPC applications to automatically send the logged on user ID in the LU6.2 attach message, when setting the security parameter to AP_SAME. Prior to this enhancement to SNA Server, setting the AP_SAME option would only transmit the USER_ID field when the program had been previously invoked with conversation security by another APPC program.
MORE INFORMATIONThis enhancement to the APPC API allows an invoking transaction program to use the current logged-on Windows NT user ID as the user ID for APPC Conversation Level security. To enable this feature:
NOTE: For a CPIC application to take advantage of this new feature, the "UnverifiedAP_SAME" setting in WIN.INI or Windows NT registry must be configured as documented above. The CPIC application must specify the CM_SECURITY_SAME option in the Set_Conversation_Security_Type (cmscst) call.
RESOLUTIONMicrosoft has updated the Windows NT client file WAPPC32.DLL, and the Windows 3.x client files, WINAPPC.DLL and WNAP.EXE, to correct this problem. Make sure that "UnverifiedAP_SAME" (or UnverifiedAP_SAME) is set as mentioned above.
STATUSThis feature is included in the latest U.S. Service Pack for SNA Server for Windows NT, version 2.11. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K REFERENCEFor additional information, please see the following article(s) in the Microsoft Knowledge Base:
ARTICLE-ID: Q163015 TITLE : Use of "Already Verified" APPC Security from Invoking TPs |
Additional query words: prodsna
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |