Page 1 of 1

Package creation

Published: June 4, 2015 - 10:51
by raiden5_5
Hello,
I don't know why, but for some time now I've been having a problem creating packages. I keep getting the message "WARNING No private key provided..." I've recreated the key several times (of course, I provide the path to the new certificate), and then when I try to install a package, it doesn't work.
My WAPT server is running Linux

Thank you in advance

Re: Package creation

Published: June 4, 2015 - 11:16
by htouvet
Package creation uses the local configuration wapt c:\wapt\wapt-get.ini

[global]
...
private_key=c:\private\my_organization.pem

Re: Package creation

Published: June 5, 2015 - 09:29
by raiden5_5
Thank you for your reply, and yes, indeed, I wasn't paying enough attention! :)
Thanks again!

I have another question: is it possible for a user to choose which software to install on their machine? (Perhaps with "show software status," but when I try to install software, it asks for credentials, and I don't know what they are for.)
And one last question: can one or more programs be installed while respecting user permissions?

These are really the last two things I need to know about using this software. I use it almost every day, and I think it's fantastic!

Thanks again for this great software! :D

Re: Package creation

Published: June 5, 2015 - 09:35
by htouvet
You can indeed install from the local console (by default http://localhost:8088 ).
The accounts authorized for installation this way are:
- local administrators of the machine
- domain administrators
- members of a group named "waptselfservice" to be created in Active Directory.

--
I didn't understand "taking into account" the permissions?
Do you want to allow certain user groups to install certain software?

Re: Package creation

Published: June 5, 2015 - 10:28
by raiden5_5
By "taking into account" the rights, I meant whether someone who isn't an administrator of the machine, but who can install software from the list of available software using the methods you indicated, would be able to do so.

But the solution with the "waptselfservice" group seems like a good one; do I just need to create this group?

Re: Package creation

Published: June 5, 2015 - 11:25
by htouvet
Yes, you need to create the waptselfservice group on the AD and put in this group the users to whom you want to give the right to install software.

Re: Package creation

Published: June 5, 2015 - 3:52 PM
by raiden5_5
Okay, thank you! :)
What I'd like to do is allow users to install only the software listed in the repository (available on localhost) and nothing else (so they can't install just anything). Is that possible?

Re: Package creation

Published: June 5, 2015 - 4:14 PM
by htouvet
Yes, that's exactly it.
We only install WAPT packages that are signed by the admin.
We don't grant permission to install just anything.

Re: Package creation

Published: June 5, 2015 - 4:23 PM
by raiden5_5
Sorry to be a pain, but I want to make sure I understand. :oops:

Once I create the "waptselfservice" group with Active Directory, will users only be able to install software available in the list of available packages? Because if I grant installation rights through Active Directory, they'll be able to install anything, right? Or does WAPT recognize "waptselfservice" and only allow installations of available packages?

Thanks again for your answers. :oops:

Re: Package creation

Published: June 5, 2015 - 4:34 PM
by htouvet
Yes, it is indeed the local waptservice that verifies user authentication and checks whether the user is an administrator or a member of the waptselfservice group.

If so, waptservice authorizes the installation/uninstallation of WAPT packages via the local waptservice service
( http://localhost:8088/install?package=toto-firefox ).

This does not grant any other rights.
(In particular, it does not change the wapt-get command-line permissions, which require full administrator privileges.)