Enhance role-based access control by adding 'ap_developer' role with scopes

kubernetes/helm/platform-api-helm-chart/values.yaml

@@ -136,8 +136,8 @@ config:
       # Roles the mapping file defines, each a name and the scopes it grants.
       # Only ap_admin is shipped here — the file-mode admin below names it.
       # platform-api/resources/role-to-scope-mapping.yaml is the full sample set (ap_admin,
-      # ap_operator, ap_publisher, ap_subscriber, ap_viewer); copy the entries you
-      # need from it. An ap: scope the Platform API's OpenAPI spec does not declare
+      # ap_operator, ap_publisher, ap_developer, ap_subscriber, ap_viewer); copy the
+      # entries you need from it. An ap: scope the Platform API's OpenAPI spec does not declare
       # fails startup; dp: scopes (API Portal) are checked for shape only.
       # A resource-level :manage already covers that resource's subresources
       # (each subresource operation lists the parent :manage in its own accepted

platform-api/README.md

@@ -348,7 +348,7 @@ key silently ignored.
 #### Role-Based Access Control (RBAC)
 
 Per-route scope checks are enforced when `platform_api.auth.authorization.enabled = true`. The
-shipped [`resources/role-to-scope-mapping.yaml`](resources/role-to-scope-mapping.yaml) defines five roles, each granting scopes in
+shipped [`resources/role-to-scope-mapping.yaml`](resources/role-to-scope-mapping.yaml) defines six roles, each granting scopes in
 both the `ap:*` (Platform API) and `dp:*` (Developer Portal) namespaces — one role covers a persona
 across both components:
 
@@ -357,6 +357,7 @@ across both components:
 | `ap_admin` | Platform administrator | Every resource and operation, both components |
 | `ap_operator` | Platform operator / CI-CD service account | Gateways, deployments, subscription plans, key managers, webhooks; reads everything else |
 | `ap_publisher` | API publisher | Full API/MCP/LLM lifecycle and its Developer Portal content; reads applications, subscriptions, plans |
+| `ap_developer` | API developer | Creates, updates and deploys APIs/proxies in an existing project and calls them through its own application and keys; can delete the MCP/LLM proxies it owns, but not REST APIs, projects or secrets, and publishes no portal content |
 | `ap_subscriber` | API consumer | Own applications, subscriptions and keys; reads the API/MCP catalog and plans |
 | `ap_viewer` | Auditor | Read-only across both components |
 
@@ -410,7 +411,7 @@ roles         = ["ap_admin"]               # expanded via auth.authorization.rol
 ```
 
 `roles` is a list, so a user whose persona spans two shipped roles names both rather than needing a
-sixth role defined for the combination — `roles = ["ap_publisher", "ap_subscriber"]` grants the union
+seventh role defined for the combination — `roles = ["ap_publisher", "ap_subscriber"]` grants the union
 of the two, most-permissive wins, with duplicate scopes collapsed.
 
 The issued token carries **both**: the expanded scopes as the `scope` claim, and the role names as the

platform-api/resources/role-to-scope-mapping.yaml

@@ -104,6 +104,68 @@ roles:
       - dp:webhook_subscriber:manage
       - dp:event:read
 
+  # API developer — builds APIs, MCP proxies and LLM proxies in an existing
+  # project and calls them through its own application; owns the proxies it
+  # creates but cannot delete REST APIs, projects or secrets.
+  - name: ap_developer
+    scopes:
+      # Platform API
+      - ap:organization:read
+      - ap:project:read
+      - ap:rest_api:create
+      - ap:rest_api:read
+      - ap:rest_api:update
+      - ap:rest_api:gateway:read
+      - ap:rest_api:gateway:create
+      - ap:rest_api:deployment:create
+      - ap:rest_api:deployment:read
+      - ap:rest_api:deployment:undeploy
+      - ap:rest_api:deployment:restore
+      - ap:rest_api:api_key:manage
+      - ap:mcp_proxy:create
+      - ap:mcp_proxy:read
+      - ap:mcp_proxy:update
+      - ap:mcp_proxy:delete
+      - ap:mcp_proxy:deployment:create
+      - ap:mcp_proxy:deployment:read
+      - ap:mcp_proxy:deployment:undeploy
+      - ap:mcp_proxy:deployment:restore
+      - ap:llm_proxy:create
+      - ap:llm_proxy:read
+      - ap:llm_proxy:update
+      - ap:llm_proxy:delete
+      - ap:llm_proxy:deployment:create
+      - ap:llm_proxy:deployment:read
+      - ap:llm_proxy:deployment:undeploy
+      - ap:llm_proxy:deployment:restore
+      - ap:llm_proxy:api_key:manage
+      - ap:llm_provider:read
+      - ap:llm_template:read
+      - ap:gateway:read
+      - ap:gateway:manifest:read
+      - ap:gateway_custom_policy:read
+      - ap:secret:create
+      - ap:secret:read
+      - ap:secret:update
+      - ap:application:manage
+      - ap:subscription:manage
+      - ap:subscription_plan:read
+      - ap:api_key:read
+      - dp:application:manage
+      - dp:application_key:manage
+      - dp:application_key:revoke
+      - dp:subscription:manage
+      - dp:api_key:manage
+      - dp:mcp_server_key:manage
+      - dp:organization:read
+      - dp:organization_content:read
+      - dp:api:read
+      - dp:mcp_server:read
+      - dp:mcp_server_content:read
+      - dp:subscription_plan:read
+      - dp:view:read
+      - dp:label:read
+      - dp:event:read
   # Platform operator / CI-CD service account — runs gateways, deployments,
   # subscription plans, key managers and webhooks; reads everything else.
   - name: ap_operator