I have installed a new pbs 4.1 server to replace my old 3.4.0 server.
It is completely unusable right now.
I am unable to add rights to the datastore for my local user (because that is the only user I am allowed to select in the pve backup server setup.
I'm really confused on how this whole thing is supposed to work.
I have a MS tenant (openid) with a app registration witch can successfully login both to pve and pbs.
But pbs are adding strange domain suffixes to the local users that I do not understand.
My test user are listed as "user@domain.com@domain.com"
Also, I am unable to use this openid user from pve as backup storage, and I am unable to add rights for the root account to the storage on the pbs server.
On my old server, the user root@pam!pbs (weird name) are admin on the backup storage, but I am unable to add this access on the 4.1 server.
The problem is the same, even if I login as root instead of the openid user (witch also has admin access on /).
I am confused. Luckily my old backup server still works.
It is completely unusable right now.
I am unable to add rights to the datastore for my local user (because that is the only user I am allowed to select in the pve backup server setup.
I'm really confused on how this whole thing is supposed to work.
I have a MS tenant (openid) with a app registration witch can successfully login both to pve and pbs.
But pbs are adding strange domain suffixes to the local users that I do not understand.
My test user are listed as "user@domain.com@domain.com"
Also, I am unable to use this openid user from pve as backup storage, and I am unable to add rights for the root account to the storage on the pbs server.
On my old server, the user root@pam!pbs (weird name) are admin on the backup storage, but I am unable to add this access on the 4.1 server.
The problem is the same, even if I login as root instead of the openid user (witch also has admin access on /).
I am confused. Luckily my old backup server still works.