Title: feat: Implement RegistryServer.Proto RPC with RBAC-filtered response · Issue #6558 · feast-dev/feast · GitHub
Open Graph Title: feat: Implement RegistryServer.Proto RPC with RBAC-filtered response · Issue #6558 · feast-dev/feast
X Title: feat: Implement RegistryServer.Proto RPC with RBAC-filtered response · Issue #6558 · feast-dev/feast
Description: Summary The Proto RPC is defined in the RegistryServer protobuf service definition but is not implemented on the server side, causing RemoteRegistry.proto() calls to fail with UNIMPLEMENTED. The method was intentionally removed to preven...
Open Graph Description: Summary The Proto RPC is defined in the RegistryServer protobuf service definition but is not implemented on the server side, causing RemoteRegistry.proto() calls to fail with UNIMPLEMENTED. The me...
X Description: Summary The Proto RPC is defined in the RegistryServer protobuf service definition but is not implemented on the server side, causing RemoteRegistry.proto() calls to fail with UNIMPLEMENTED. The me...
Opengraph URL: https://github.com/feast-dev/feast/issues/6558
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"feat: Implement RegistryServer.Proto RPC with RBAC-filtered response","articleBody":"## Summary\n\nThe `Proto` RPC is defined in the `RegistryServer` protobuf service definition but is not implemented on the server side, causing `RemoteRegistry.proto()` calls to fail with `UNIMPLEMENTED`. The method was intentionally removed to prevent bypassing RBAC, since a raw passthrough of `proxied_registry.proto()` returns the entire registry without any permission checks.\n\n## Problem\n\n- `RemoteRegistry.proto()` calls `stub.Proto(Empty())` which fails because the server never implements the RPC.\n- This breaks any code path that relies on `BaseRegistry.proto()` when using a remote registry (e.g., cache initialization in `CachingRegistry`, registry refresh, metrics collection).\n- Simply re-adding `return self.proxied_registry.proto()` would reintroduce the RBAC bypass — all objects (entities, feature views, data sources, permissions, projects, etc.) would be returned regardless of the caller's authorization.\n\n## Proposed Solution\n\nImplement `RegistryServer.Proto` by assembling the `RegistryProto` response from individual RBAC-filtered list calls, consistent with how every other RPC on `RegistryServer` enforces permissions:\n\n- Use `permitted_resources()` with `AuthzedAction.DESCRIBE` for each object type (projects, entities, data sources, feature views, feature services, saved datasets, permissions, etc.).\n- Construct and return a `RegistryProto` containing only objects the caller is authorized to see.\n\nThis ensures:\n1. The proto service contract is honored (no `UNIMPLEMENTED` error).\n2. `RemoteRegistry` works correctly as a `BaseRegistry` implementation.\n3. RBAC is enforced — callers only see objects they have `DESCRIBE` access to.\n","author":{"url":"https://github.com/ntkathole","@type":"Person","name":"ntkathole"},"datePublished":"2026-06-26T05:19:35Z","url":"https://github.com/feast-dev/feast/issues/6558"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:5b0049d4-883e-8f80-0d65-882007a24bce |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 832E:EFEB1:F4C5C3:141F06D:6AFE9810 |
| html-safe-nonce | 9ea084a32505378980bfc11b81cce6e81b7724004c2d290d5971e2bc1757d381 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI4MzJFOkVGRUIxOkY0QzVDMzoxNDFGMDZEOjZBRkU5ODEwIiwidmlzaXRvcl9pZCI6IjI5ODc2MTk2OTg1OTk2OTY0MDAiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | bb7901cb54d64878c344f0d43d5e523f322a3eff7f8c2a6c427833519703e043 |
| hovercard-subject-tag | issue:4749468898 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/feast-dev/feast/6558/issue_layout |
| twitter:image | https://opengraph.githubassets.com/84081ae8016250fa312c2f00a7f166297bdbfa607f7fd3a4452caba5d12f2e84/feast-dev/feast/issues/6558 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/84081ae8016250fa312c2f00a7f166297bdbfa607f7fd3a4452caba5d12f2e84/feast-dev/feast/issues/6558 |
| og:image:alt | Summary The Proto RPC is defined in the RegistryServer protobuf service definition but is not implemented on the server side, causing RemoteRegistry.proto() calls to fail with UNIMPLEMENTED. The me... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | ntkathole |
| hostname | github.com |
| expected-hostname | github.com |
| None | b3c0f155eafc27e60db6e254d1ffff0e072e9ab3b4018a5ee518797c19d89f86 |
| turbo-cache-control | no-preview |
| go-import | github.com/feast-dev/feast git https://github.com/feast-dev/feast.git |
| octolytics-dimension-user_id | 57027613 |
| octolytics-dimension-user_login | feast-dev |
| octolytics-dimension-repository_id | 161133770 |
| octolytics-dimension-repository_nwo | feast-dev/feast |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 161133770 |
| octolytics-dimension-repository_network_root_nwo | feast-dev/feast |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 4a10310af51a1bfffbedc4fd81cb582acf0cb0ff |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width