Page 1 of 1

[SOLVED] Private key not found on dev machine

Published: March 12, 2018 - 10:33
by Eric
Hello,

I am currently testing the new version 1.5 (RC1). The server is running Debian, and the development machine is running Windows 10, as is the management console PC.

On the development PC, I can't import packages or modify the machine's configuration (in fact, the "Check for updates" and "Start installations" buttons are grayed out). Each time, a window opens with the message:
"Private key does not exist."
I can't understand why it can't find the key, even though it's located in c:\private, as indicated in the documentation, and it's correctly entered in the files c:\Program Files (x86)\wapt\wapt-get.ini and appdata\local\waptconsole\waptconsole.ini. However,
in my appdata\roaming\waptconsole|waptconsole.ini, I only have settings related to the console's graphical interface, and in appdata\roaming\wapt, I only have a waptsession.sqlite file.

Note: I haven't enabled authentication. Kerberos, for now.

If someone could shed some light on this...

I know this version is brand new, and it's normal that the documentation isn't perfect yet, but I'd like to make a suggestion: it would be helpful to have a clear and precise description of the security system implemented in this new version (user authentication, machine authentication, with or without Kerberos...). It could be useful.

Thanks for your work

.

Re: Private key not found on dev machine

Published: March 12, 2018 - 11:01
by Eric
Hi,

I forgot to mention: I'm on the community version.

Re: Private key not found on dev machine

Published: March 12, 2018 - 11:32
by Eric
I'm answering myself (as usual, I've been trying to figure out what's wrong for ages, and it's only when you ask the question that you find the answer yourself):

I was missing a line in the file appdata\roaming\waptconsole|waptconsole.ini:

Code: Select all

personal_certificate_path=c:\private\certifserveur.crt
I can't find anything in the documentation about the files in the user's appdata folder. So I assume they're supposed to generate themselves. Is it a bug? A problem during agent creation? I didn't have this kind of problem with WAPT 1.3, anyway.

AND.

Re: Private key not found on dev machine

Published: March 12, 2018 - 11:59 PM
by htouvet