Just wondering if im doing anything wrong before opening an issue. Creating a Microsoft Entra ID identity provider, returns an error "This providerId is reserved and cannot be used for an SSO provider". I'm wondering if the underlying OIDC auth library has reserved the providerid "EntraID"

Hi I am Minakshi, I am planning to try out Agentic AI so joined this community. Thanks for all your help in advance.

With github.com/archestra-ai/archestra/pull/6488 was the intention on this to hard block all access to the following ranges from MCP pods with no way to override if the environments networkPolicy is set to unrestricted (Allow All)?:

- 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 - RFC 1918 private ranges (cluster pods, services, nodes) <--- This is the primary one I'm wondering about

- 169.254.0.0/16 - Link-local / cloud metadata endpoints (AWS IMDSv1, GCP, Azure)

- 100.64.0.0/10 - Carrier-grade NAT (RFC 6598)

-- 127.0.0.0/8 - Loopback

-- 0.0.0.0/32 - Treated as localhost by some HTTP libraries

Hi i have been testing out archestra to see if it would fit our companies needs, but i have a couple of question i cant figure out.

1. When i create an mcp registry and attach it to a gateway is there a way of having for each user it's own "identity"/"credentials" that the mcp from the registry could connect to or do i need to register for each user its own mcp (example is linear mcp). The goal is that if user X uses the mcp gateway it will use the registered linear mcp with his credentials instead of a shared one. Would we register for each user it's own MCP of linear?

2. Is there anything on the roadmap for having more layers than organizational - team - personal? We would love to have nested teams/projects