PBS 4.1 breaks access from pve

Scifibob

Member
Jun 4, 2023
12
0
6
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.
 
I have tried several things, and is not that confused anymore.
The only problem remaining, is that I need to input the fingerprint of my LetsEncrypt certificate.
But that is a separate bug.
1. I needed to create an API key for the root user.
2. I needed to give access for this API, which seems to be the root user, but with an API key. This is where my confusement started.
3. Then I needed to add the storage to my pve server, with the root user (root@pve!pbs), the API key as password, and my LetsEncrypt cert fingerprint.
I have to say, this could me made very much simpler.

Because I use a MS app registration as login, I kept confusing the user names and domains (or realms, as Proxmox calls them).
They are all over the place, like "user@mydomain.com@mydomain.com" or "user@pbs!something".