Authorized key list file - connect_cdc_sqdata - 4.1

Connect CDC (SQData) Secure communications components

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (SQData)
Version
4.1
Language
English
Product name
Connect CDC (SQData)
Title
Connect CDC (SQData) Secure communications components
Topic type
How Do I
Installation
Copyright
2024
First publish date
2000
ft:lastEdition
2024-02-07
ft:lastPublication
2024-02-07T13:29:14.268926

This list is merely a concatenation of the content of the public keys of the users authorized to use the services of the Controller Daemon. If the Controller Daemon cannot find the public key presented by the client in its authorized keys list, and the Controller Daemon is not configured to allow guest users, then the client is informed that its key is not authorized and the connection is closed.

Each platform in the environment running a Controller Daemon will typically have an entry in the Authorized Key List for the Controller Daemons running on other host machines in the environment. While not necessarily recommended, all the Daemons can share the same public/private key pair or a new one can be generated for each Controller Daemon/Platform.

Publishers that have been configured to perform NaCL Payload Encryption for one or more subscribing Engines, require their own Authorized Key List File. It should contains the Public Keys for only those Engines that will receive the Encrypted data. While initially the contents of the file may be identical to that of the Publisher's Controller Daemon, that may change over time as additional Publisher agents are added to a single SQDAEMON, each with one or more subscribing Engines.

Sample Authorized key list - NACL.AUTH.KEYS
YO1rxrBqeaROEaNj176165MGoB4MgxGXN0m8BvpDCBs= SQDUSER1@ZOS1
5Y3FJbqOSaaImePo7fMb4I9Zm3Cw8H1oa4gVoF9Tazg= SQDUSER2@linux2
LtfZXhmS61tTRElodV1RTzN+dt086dQpJ0U830wnoaY= SQDUSER3@aix3