👀 Views: 24 💬 Answers: 1 📅 Created: 2025-06-26

oci api-gateway iam functions plaintext

I'm wondering if anyone has experience with I'm working on a personal project and I'm stuck on something that should probably be simple... I'm currently working with a scenario with the OCI API Gateway where I'm receiving a `403 Forbidden` behavior when attempting to invoke my backend service, which is an OCI Function. I've already set up the API Gateway and the Function correctly, but it seems like the IAM policy related to permissions is preventing the call. Here's the IAM policy I've created: ```plaintext Allow group myGroup to manage functions in compartment myCompartment ``` I verified that the API Gateway is integrated with the correct compartment and has the proper permissions associated with the user invoking it. On the API Gateway, I set up a route that points to my function with the following configuration: ```json { "uri": "https://functions.us-ashburn-1.oci.oraclecloud.com/20181201/functions/myFunction/invoke", "method": "POST" } ``` I also ensured that the API Gateway is set up to use the correct authentication type, which is the `OCI IAM` method. Despite these configurations, I keep getting the behavior when I try to invoke the API endpoint from Postman. Here's the behavior response I'm receiving: ```json { "code": "Forbidden", "message": "You are not authorized to perform this operation." } ``` I've tried adding additional policies like: ```plaintext Allow group myGroup to use api-gateways in compartment myCompartment ``` But the scenario continues. I've double-checked the `auth` settings in my API Gateway and the function's access settings. Has anyone encountered this scenario or can provide insights into what might be wrong with the IAM policy or any missing configurations that could be causing this behavior? For context: I'm using Plaintext on Linux. How would you solve this? The stack includes Plaintext and several other technologies.