In reply to: Robert
In my case i didn't have AD, i used local account. I created AD, and I ran webcon BPS system administrators file and added myself to the config database and everything working now
I just installed a production environment on a server without AD connection. It's the same version 2022.1.2.31 as the test environment and on the production I ran into the issue that the user was authenticated, welcome user name, was displayed but wasn't authorized, you don't have permissions to use the designer studio.
Activating the license didn't help and the user was already added as a system administrator using the mentioned tool.
Since I had two very similar environments I was able to fix my issue:
1. Add the local account to CacheOrganizationStructure of the created content database(s).
INSERT INTO [dbo].[CacheOrganizationStructure]
(
[COS_IsActive]
,[COS_AccountType]
,[COS_ProviderType]
,[COS_Login]
,[COS_BpsID])
VALUES
(1,1,6,'COMPUTERNAME\accountname','COMPUTERNAME\accountname')
2. iisreset
I confirmed that this worked, on my environment, by deleting the created entry and doing an iisreset. I was immediately greeted with the infamous no permissions page.
I did test this a few times and it seemed to work reliable.
While searching for a solution I did also restart the service, but it didn't seem to have any effect.
Edit:
I've run into another issue afterwards. I opted to uninstall everything, deleting application pool, IIS site and database. The new installation worked without flaws.