A place to ask questions, connect with others, and stay in the know
C:\GCTI\APPS\CS> .\confserv.exe -c C:\EncrypTest\pass.txt -p Section1 "abc123"
Genesys Configuration Server. Version 188.8.131.52
Copyright (c) 1997-2020 Genesys Telecommunications Laboratories, Inc.
Build information :
Description : (Content Freeze)
Timestamp : Jan 27 2021 23:23:20
Version : 184.108.40.206
Configuration library v.220.127.116.11
Common library v.18.104.22.168 C2 MT-Safe
Service library v.22.214.171.124 MT
Message library v.126.96.36.199
Log library v.188.8.131.52 MT
LCA library v.184.108.40.206
Thread library v.220.127.116.11
DBServer library v.18.104.22.168
Genesys License library v.none
License library v.none
Stat Script library v.8.5.106.05
Database password encrypted in the configuration file
password=004028550714770F <<~~ Encrypted password
[confserv] <<~~ Added automatically by confserv executable
Hi Tony,Thanks for that, things might have gone better if we were in the same timezone and just had a phone conversation. I agree that we were not on the same wavelength. I do apologize.The Genesys silent install is described in the framework deployment guide (page 225). This only works for the servers: • Configuration Server• Message Server• Solution Control Server• T-Server• HA Proxy• Stat ServerMy understanding is that you have a custom PSDK application that needs to authenticate against config server and you want to hold the password in non clear text.Looking at the PSDK documentation, you need to specify the Username, Application name and password at the time of the ConfServerProtocol.open() function call.At this point you need to have the password in clear text. As far as I can tell there is no way around this.What you can do is write a basic custom encrypt/decrypt function. The encrypt is a standalone program that you use to generate your "encrypted" text for your custom ini file. In your code you you reverse this process at runtime. Clearly this is not going to be high grade security as the encryption key would need to be hard coded in your routines.
I talked to some developers and they would use something like base64 encode/decode. It is marginally better than plain text, but its not real security.
From a security perspective you could use the operating system permissions to protect the .ini file, so the only person that could read the file would have the password anyway.Alternately I suppose you could rely on SSO, so you would not need the cfg password.I hope this helps.If not then please raise a new case and we can ask engineering how they implemented Silent Install.RegardsAndrew
Every year, Genesys® delivers more than 70 billion remarkable customer experiences for organizations in over 100 countries. Through the power of the cloud and AI, our technology connects every customer moment across marketing, sales and service on any channel, while also improving employee experiences. Genesys pioneered Experience as a ServiceSM so organizations of any size can provide true personalization at scale, interact with empathy, and foster customer trust and loyalty. This is enabled by Genesys Cloud™, an all-in-one solution and the world's leading public cloud contact center platform, designed for rapid innovation, scalability and flexibility. Visit www.genesys.com.