Central Business Configuration (CBC) Authorization Error / Unauthorized Suddenly

[NelsenW_]

I have been using S/4HANA Cloud Public Edition for a long time. Previously i can access the CBC normally and i am the one who setting the config for S/4HANA. I am admin for my company system too, so i can access IAS...

Today i tried to give my coworker access to CBC, and it worked. But suddenly after that i cannot access CBC anymore. It said "Unauthorized".

I have tried various ways :

1. I check my user in IAS, and i have the access to CBC

2. I Resync IAS for the CBC multiple times

3. I deleted my user in the IAS and make a new user with the same email, and assign it to my CBC again. but it didnt work



Please help, what can i do again? It suddenly unauthorized my user from CBC, but in IAS it show that my user has the access

SAP Central Business Configuration SAP S/4HANA Cloud Public Edition 

[TamasFodor]

Hi, We helped you to accept the answer, since there were no updates after a few days. You can unaccept it anytime if you have further questions. Kind regards, Tamas SAP Community Topic Expert

[Lucian · Accepted solution]

Hi @NelsenW_ 

this problem can occur if you have changed your login name value in the IAS or tried to access the system before the user replication was finalized with different login attributes in the application SNI parameter (email)

Unauthorized error could point here, based on your description, to the old access certificate stored with the previous login name(s) used in the last valid access session.

Please check the note 

3385412 - Access to SAP Central Business Configuration fails with error "You are not logged in or yo...

and the status of the configuration described there that is needed to automate the cached data used  in the XSUAA service.

If this is not setup yet you need to open a case to X4-CBC-SRV and request setup credentials.

You will find in the note attachments step by step instructions and a sample json file that you can use to create this additional target in IAS.

Once this is done trigger a  new provisioning job and the cached data should be updated  in the BTP subaccount for your user restoring the access for you to the system with the latest login name used and replicated from IAS.

Regards,

Lucian