Communication Database

Cuneyt Goksu

Communication Database
Hello Db2 Community;

This is an old problem but I could not remember the solution anywhere yet.

I hope someone will remember that.



I've configured Communication Database to access from Db2z to distributed
DB2, basically it is an outbound request.

The goal is NOT to give any passwords for target platform in USERNAMES
table.

As you know AUTHID in USERNAMES table is mapped to NEWAUTHID and PASSWORD in
USERNAMES and send to remote server for authorization. This is not preferred
since the Pwd of the remote server is visible in USERNAMES table.



If you remember the definitions for SYSIBM.IPNAMES, SYSIBM.USERNAMES for
such a goal which is mentioned above, will you pls let me know what was the
settings for



SECURITY_OUT for IPNAMES

USERNAMES for IPNAMES

TYPE for USERNAMES



Thanks in advance,

Cuneyt

Nadir Doctor

Communication Database
(in response to Cuneyt Goksu)
Hi Cuneyt,

Scenario 1 of Raul's article below will aid in your connectivity
definitions -

https://www.ibm.com/developerworks/data/library/techarticle/0310chong/0310chong.html


Best Regards,
Nadir


On Fri, Nov 3, 2017 at 4:28 PM, Cuneyt Goksu (GMail) <[login to unmask email]>
wrote:

> Hello Db2 Community;
>
> This is an old problem but I could not remember the solution anywhere yet.
>
> I hope someone will remember that.
>
>
>
> I’ve configured Communication Database to access from Db2z to distributed
> DB2, basically it is an outbound request.
>
> The goal is NOT to give any passwords for target platform in USERNAMES
> table.
>
> As you know AUTHID in USERNAMES table is mapped to NEWAUTHID and PASSWORD
> in USERNAMES and send to remote server for authorization. This is not
> preferred since the Pwd of the remote server is visible in USERNAMES
> table.
>
>
>
> If you remember the definitions for SYSIBM.IPNAMES, SYSIBM.USERNAMES for
> such a goal which is mentioned above, will you pls let me know what was
> the settings for
>
>
>
> SECURITY_OUT for IPNAMES
>
> USERNAMES for IPNAMES
>
> TYPE for USERNAMES
>
>
>
> Thanks in advance,
>
> Cuneyt
>
> -----End Original Message-----
>

Michael Arlebrandt

Communication Database
(in response to Cuneyt Goksu)
Hi Cuneyt,

There is an option to encrypt the authid and password in sysibm.usernames using the encryption stored procedure SYSPROC.DSNLEUSR


regards
Michael Arlebrandt
Den 3 nov. 2017, kI 22:29, "Cuneyt Goksu (GMail)" <[login to unmask email]<mailto:[login to unmask email]>> skrev:
Hello Db2 Community;
This is an old problem but I could not remember the solution anywhere yet.
I hope someone will remember that.


I’ve configured Communication Database to access from Db2z to distributed DB2, basically it is an outbound request.
The goal is NOT to give any passwords for target platform in USERNAMES table.
As you know AUTHID in USERNAMES table is mapped to NEWAUTHID and PASSWORD in USERNAMES and send to remote server for authorization. This is not preferred since the Pwd of the remote server is visible in USERNAMES table.


If you remember the definitions for SYSIBM.IPNAMES, SYSIBM.USERNAMES for such a goal which is mentioned above, will you pls let me know what was the settings for


SECURITY_OUT for IPNAMES
USERNAMES for IPNAMES
TYPE for USERNAMES


Thanks in advance,
Cuneyt

-----End Original Message-----


::DISCLAIMER::
----------------------------------------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and other defects.

----------------------------------------------------------------------------------------------------------------------------------------------------