Too future readers, managed to fix this by editing the JS of proxmox that actually sets the cookie.
This file: /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js
Find the line that handles the auth cookie and change it from this:
JavaScript:
setAuthData: function (data) {
Proxmox.UserName = data.username;
Proxmox.LoggedOut = data.LoggedOut;
// creates a session cookie (expire = null)
// that way the cookie gets deleted after the browser window is closed
if (data.ticket) {
Proxmox.CSRFPreventionToken = data.CSRFPreventionToken;
Ext.util.Cookies.set(
Proxmox.Setup.auth_cookie_name,
data.ticket,
null,
'/',
null,
true,
'lax',
);
}
To this:
JavaScript:
setAuthData: function (data) {
Proxmox.UserName = data.username;
Proxmox.LoggedOut = data.LoggedOut;
// creates a session cookie (expire = null)
// that way the cookie gets deleted after the browser window is closed
if (data.ticket) {
Proxmox.CSRFPreventionToken = data.CSRFPreventionToken;
var expires = new Date();
expires.setDate(expires.getDate() + 365);
Ext.util.Cookies.set(
Proxmox.Setup.auth_cookie_name,
data.ticket,
expires,
'/',
null,
true,
'lax',
);
}
This example creates a new variable called "expires" which we then set proxmox to use instead of null for the date, since this creates a cookie that expires in 1 year.
Yeah I get the session cookie thing for a security standpoint and enterprise perspective, but I think you should have the option to enable saving of login sessions regardless. If admins want to configure the session cookie method for their enterprise users, they can, but home users like myself should be able to select between the two regardless.
