API authentication with cookies

Questions about WAPT Server / Requests and help related to the WAPT server
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Locked
mayasd
Messages: 2
Registration: May 22, 2018 - 1:33 p.m.

May 22, 2018 - 1:36 PM

Hello,

is it possible to authenticate to the API using a cookie or token? If not, is this planned for a future version?
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

May 23, 2018 - 10:58

Hello Mayasd,
mayasd wrote: May 22, 2018 - 1:36 PM Is it possible to authenticate to the API with a cookie or token? If not, is this planned for a future version?
The various actions initiated by the console are authenticated with a session. You must authenticate once, then you can use a token. That said, these are not persistent sessions, nor are they API tokens. There is no roadmap for that.

Regarding your WAPT web interface project, do you intend to create an interface solely for viewing or for more advanced features such as package editing, etc.? WAPT security is based on signatures and private keys, and the private key should not be hosted on a web server, as this compromises the security model.

Sincerely,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
mayasd
Messages: 2
Registration: May 22, 2018 - 1:33 p.m.

May 28, 2018 - 1:49 PM

The various actions initiated by the console are authenticated with a session. You must authenticate once, then you can use a token. That said, these are not persistent sessions, nor are they API tokens. There is no roadmap for that.
Thank you, it does indeed work.

Regarding your WAPT web interface project, do you intend to create an interface solely for viewing or for more advanced features such as package editing, etc.? WAPT security is based on signatures and private keys, and the private key should not be hosted on a web server, as this compromises the security model.

Sincerely,

Denis
For the moment there is nothing in the immediate future regarding the creation or editing of packages and if that were to happen, we take careful note of how you have implemented security.
Locked