AVEVA Global. Release 12.0.SP6 WCF. User Bulletin

Transcription

1 AVEVA Global Release 12.0.SP6 WCF User Bulletin

2 Disclaimer Information of a technical nature, and particulars of the product and its use, is given by AVEVA Solutions Limited and its subsidiaries without warranty. AVEVA Solutions Limited and its subsidiaries disclaim any and all warranties and conditions, expressed or implied, to the fullest extent permitted by law. Neither the author nor AVEVA Solutions Limited, or any of its subsidiaries, shall be liable to any person or entity for any actions, claims, loss or damage arising from the use or possession of any information, particulars, or errors in this publication, or any incorrect use of the product, whatsoever. Copyright Copyright and all other intellectual property rights in this manual and the associated software, and every part of it (including source code, object code, any data contained in it, the manual and any other documentation supplied with it) belongs to AVEVA Solutions Limited or its subsidiaries. All other rights are reserved to AVEVA Solutions Limited and its subsidiaries. The information contained in this document is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without the prior written permission of AVEVA Solutions Limited Where such permission is granted, it expressly requires that this Disclaimer and Copyright notice is prominently displayed at the beginning of every copy that is made. The manual and associated documentation may not be adapted, reproduced, or copied, in any material or electronic form, without the prior written permission of AVEVA Solutions Limited. The user may also not reverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of the product described in this publication may be incorporated into any third-party software, product, machine, or system without the prior written permission of AVEVA Solutions Limited, save as permitted by law. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminal prosecution. The AVEVA products described in this guide are to be installed and operated strictly in accordance with the terms and conditions of the respective licence agreements, and in accordance with the relevant User Documentation. Unauthorised or unlicensed use of the product is strictly prohibited. First published 2010 AVEVA Solutions Limited and its subsidiaries AVEVA Solutions Limited, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom. Trademarks AVEVA and Tribon are registered trademarks of AVEVA Solutions Limited or its subsidiaries. Unauthorised use of the AVEVA or Tribon trademarks is strictly forbidden. AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Limited or its subsidiaries, registered in the UK, Europe and other countries (worldwide). The copyright, trade mark rights, or other intellectual property rights in any other product, its name or logo belongs to its respective owner.

3 Global WCF User Bulletin Contents 1 INTRODUCTION ABOUT THIS SOFTWARE RELEASE ABOUT THIS MANUAL Who should read this Bulletin SOFTWARE DISTRIBUTION & INSTALLATION Installation SECURE COMMUNICATIONS Messages SECURITY OVERVIEW ENABLING WCF TRANSPORT LEVEL BINDINGS PORTS ENCRYPTION ENCODING AUTHENTICATION Certification Authentication AVEVA Solutions Ltd i Unclassified

4 Backing page 2010 AVEVA Solutions Ltd ii Unclassified

5 Global WCF User Bulletin 1 Introduction 1.1 About this software release The Global Server release AVEVA Global Server 12.0.SP6 WCF Update is available from the AVEVA product download site. The Global Client release AVEVA PDMS 12.0.SP6 Global WCF Update and AVEVA Hull and Outfitting 12.0.SP6 Global WCF Update are available from the AVEVA product download site. All releases self-install using standard Microsoft installation procedures. The Global Server release can be installed independently of the client PDMS or Hull and Outfitting client releases and vice versa. However, neither of these releases will work with an old installation of the other. Please note that 12.0.SP6 onwards requires Flexman 5.1 and an appropriate licence it will not work with Flexman 3 or 4. For further details of Flexman Licence Server releases, please see: About this manual This manual gives an overview of the security features provided by the Global WCF release. Global now makes use of Microsoft Windows Communications Foundation (WCF) as provided by.net 3 and above for more secure communications. The purpose of this document is to provide the reader with an overview of the security features available in the Global WCF releases. For further details, including configuration please se the Global Server WCF Configuration guide Who should read this Bulletin This guide is useful for anybody considering the security needs for Global, and should provide information to IT Administrators as much as it does to Project Administrators. 1.3 Software distribution & installation The installation process for both Server and Client installations now use Microsoft Installer (MSI) technology, which facilitates silent installations through standard MSI means. These are triggered from a setup file. The client installations AVEVA PDMS 12.0.SP6 Global WCF Update and AVEVA Hull and Outfitting 12.0.SP6 Global WCF Update need to be installed on any machine where PDMS or Hull and Outfitting needs to run a Global command (e.g. Administrator for Global projects, or where Engineers need to use distributed extracts). The Server installation AVEVA Global Server 12.0.SP6 WCF Update needs to be installed on any machines where the daemon currently runs Installation The detailed Installation process has been defined in the release notes. It is not necessary to have an existing installation of the AVEVA Global Server 12.0.SP6 installed prior to installation. Likewise it is not necessary to have either the AVEVA PDMS 12.0.SP6 or AVEVA Hull and Outfitting 12.0.SP6 installed for 2010 AVEVA Solutions Ltd 1-1 Unclassified

6 the client install. However, if an earlier version of 12.0.SP6 Global client or Global server is pre-installed this will not affect installation. Note: Installing the AVEVA Global Server 12.0.SP6 WCF Update product will not allow you to select the destination folder. Therefore if you are installing without having pre-installed AVEVA Global Server 12.0.SP6 the installation will automatically be installed to the C:\AVEVA\GlobalServer12.0.SP6 folder. 1.4 Secure Communications Traditionally Global has relied on using the Remote Procedure Call (RPC) process for communicating between PDMS and the Daemon, as well as between Daemons. This has served well when projects required heterogeneous Operating Systems such as SG-Irix, HP-UX and MS-Windows. However, in recent years, the Microsoft implementation of RPC has been exposed to a number of security threats. To eliminate the risk of an attack, AVEVA has reviewed, along with Microsoft, the use of RPC for its communication layer and as a result have implemented the Windows Communication Foundation (WCF), supplied by Microsoft, as a replacement communications layer. The key feature of using WCF is that it abstracts security away from the code. Security is now applied by the.net Framework and the Operating System, and is configured through the modification of XML files that live along side the application. The high configurability of WCF means that the system can meet the security requirements of individual IT departments through a number of changes within the configuration file rather than the security features being determined by the AVEVA development team Messages Regardless of the selected protocol Global WCF transmits data use SOAP Messages in XML. The term Message is used to represent a transmission whether it is a page of a database or file, or Global command or query AVEVA Solutions Ltd 1-2 Unclassified

7 2 Security Overview By replacing the existing Global Remote Procedure Call (RPC) communication layer with Windows Communication Foundation (WCF) Global is able to take advantage of tighter security for all PDMS/Hull and Outfitting to Daemon and Daemon to Daemon communications. Microsoft has developed WCF with the purpose of ensuring the high demands of corporate IT demands can be met. By providing a highly configurable mechanism WCF abstracts security from code, placing the control on the level of security for each connection in the hands of the Project and IT Administrators rather than in the application itself. As a result it is very easy to define a project network that can cross Trust Boundaries safely whilst protecting corporate networks from malicious attacks. This section outlines the security features provided by WCF, for details on how to configure Global to best utilise these features please refer to the configuration details in the Global Server WCF Configuration Guide. The AVEVA Global Server 12.0.SP6 WCF Update, AVEVA PDMS 12.0.SP6 Global WCF Update and AVEVA Hull and Outfitting 12.0.SP6 Global Update releases a re all Security updates. There is not further Global functionality provided. 2.1 Enabling WCF By default the system is configured to run in existing RPC mode. To enable the use of WCF the GLOBAL_PROTOCOL tag must be changed from RPC to WCF in the AVEVA PDMS 12.0.SP6 Global WCF Update or AVEVA Hull and Outfitting 12.0.SP6 Global WCF Update globalwcfclient,config file. Enabling the WCF communication layer will default to using the HTTP binding on Port 8000 with no security. Details on how to switch to the communications layer to WCF and on Security settings are available in the Global WCF Configuration guide. 2.2 Transport Level The Transport Level determines whether to apply any security to messages, and if so at what level. There are three settings that can be applied:- None Security is not applied to messages Transport Level Security End to End Security is applied. This is the process of ensuring the connection rather than individual messages. The message can only be validated once, and has to be trusted there after. Message Level Security Peer to Peer Security is applied. Security is encapsulated in the message itself. Every message needs to be verified. This suffers from poorer performance compared to Transport Level security as each Message MUST be verified. 2.3 Bindings It is possible to select the low level protocol for transfer of the Messages, enabling the best protocol to suit the security requirements for the communication. The protocols that are available to select from are: AVEVA Solutions Ltd 2-3 Unclassified

8 Transmission Control Protocol (TCP) This is the same protocol used by the RPC Daemon. Data is sent in binary encoding (please see section on encoding) and is not visible to external security checks, however as a result transfer is faster. HyperText Transfer Protocol (HTTP) Data is sent in text encoding, which is verbose compared to binary and has an impact on performance. However, as the Messages are in text they can be inspected by an external validation program. Web Services HyperText Protocol (wshttp) This is the same as HTTP, but the Messages are encrypted. As a result the Messages cannot be inspected by an external valuator. 2.4 Ports The WCF Global Daemon requires only 1 port for communication, and this can be any port. It is best to use a dedicated port (one selected for the dynamic range that is not used by an alternative application) to ensure that there is no contention with other applications. If Firewalls have been configured to use a restricted dynamic port range already, then one of these can be selected to make use of current Firewall settings. It is possible to use a well known port (such as Port 80 for HTTP) if desired. Note: When multiple projects are running it maybe desirable to use different ports for different projects to avoid contention. Choice of binding may affect the best default port to use. All ports in the sample files provided use Port 8000 Note: Although it is possible to use Port 135 for communications this should be discouraged. Port 135 is a high risk port susceptible to attack. If possible this Port should be closed when using WCF. 2.5 Encryption It is possible to encrypt Messages on transmission. This protects the Message from being interpreted by an illegal external application. There are a number of algorithms for encryption/decryption supplied by the.net Framework that WCF can exploit, but it is possible to use a propriety algorithm if preferred. Default encryption is 128bit, but algorithms up to 256bit are available. Algorithms below 128bit may not be fully protected. 2.6 Encoding The encoding used determines the format of the message, and is linked to the binding selected. There are 3 levels of encoding available:- Text As mentioned in the Binding section Text encoding is verbose and therefore suffers from slower performance, but the content of the Message can be inspected. Binary Binary encoding has higher performance, but as the data is binary the conmtent cannot be inspected. Message Transmission Optimisation Mechanism (MTOM) This third method of encoding strikes a balance between performance and security by mixing the encoding used within the Message. MTOM encodes much of the Message in text, but uses binary for sending attachments. The message content can be partially inspected where values are in text, and large data sections can be sent faster. 2.7 Authentication Authentication is the process of ensuring that a Message is sent for a known source and receiver by a known receiver. Depending on the Transport Level chosen (either Transport or Message) Authentication can be applied to the connection, or to each individual Message. Using Transport Level Security the 2010 AVEVA Solutions Ltd 2-4 Unclassified

9 connection is authenticated; using Message Level Security each individual Message contains the authentication details. There are 2 ways of authenticating Messages:- Windows Login Accounts Assuming that the locations are within the same domain and access the same Window User accounts it is possible to authenticate against a Windows login account. Certification Use of a Certificate as provided by a Root Authority (such as VeriSign) for authentication Certification Authentication The use of certificates when sending messages between locations ensures that the message is authenticated by applying a certificate to the message or connection. Certificates can be obtained from external companies known as registration authorities (also known as root authorities) such as VeriSign or Thawte. Certificates use Public and Private keys (supplied with the certificate at request) to verify that the messages meets the certificate credentials. Once the certificate has been received and the private keys are installed into the local trust store, it is possible to authenticate messages against the certificate. Validation of the certificate is mutual, that is the sender ensures it is sending the message to a known receiver, and the receiver ensures that the message is from a known sender AVEVA Solutions Ltd 2-5 Unclassified