Unable to register cloud script (azure) function anymore

Question

question

Martin asked 3 days ago

Unable to register cloud script (azure) function anymore

I have previously successfuly registered few azure functions. Now when I try to register another one I get "Action not authorized by title. : Action not authorized by title". I was looking for some setting in Title settings but I do not see anything to prevent it.

I was changing some API Policy some time ago so I think that is the cause, but I can't find which policy is responsible for this. I have pfrn:api--/Admin/ and pfrn:api--/Server/ Allow. I tried to add pfrn:api--/CloudScript/* but it does not work.

Edit: after setting the policy to pfrn:api--* Allow and waiting few hours, it started working again. I would like to know which specific policy controls this functionality.

apis CloudScript

1

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Martin commented · 3 days ago

I replaced all my api policy with pfrn:api--* Allow, but it still does not allow me to add another cloud function. Edit: the next day it worked.

0 ·

Answer 1 · 2023-03-17T09:37:57Z

Xiao Zha answered 3 days ago

I have changed the policy to test the RegisterHttpFunction API, but cannot reproduce your issue, it works fine in my test. You may check the API policy and the Global Entity policy to see if there is any difference from the normal one (which you can get from a new created Title).

1

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Martin commented · 3 days ago

Before I changed my policy I saved the default one. I can't identify which policy statement allow/deny RegisterHttpFunction in the default api policy, because it is not explicitly stated among the default statements.

It seems that the changes take some time to manifest because I set allow all policy yesterday and it didn't work even few minutes after, but the next day it worked.

My custom changed policy was to allow all for Admin and Server and then enumerate specific client calls that are allowed (GetLeaderboard etc). With this policy, I get the "Action not authorized by title" consitently.

0 ·

question