AIFACTORY-FEAT-089: Trusted tenant and project scope from the edge to a service¶
Generated from the architecture model
This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
A design artefact, not a tracker
This backlog is generated from model/backlog/ and validated against the architecture model. No work item exists in any tracker, and no item carries a date, an estimate or an assignee (ADR-0029).
Epic Engineering readiness · Increment I0 Readiness · State elaborated · Route backend-developer · Build order 45 of 185 (Factory code)
Every call in the Factory carries a tenant and project scope that was established once, at the edge, from a token of the Identity Platform, and no service trusts a scope a caller merely claims. This is the first capability every other one depends on.
| Delivers | — |
| Stubs | — |
| Realizes | adrs: ADR-0015 bounded contexts: BC-32 |
| Requirements | — |
| Depends on | — |
| Sources | docs/architecture/capability-dependencies.md, docs/ai-software-factory/current-state.md |
AIFACTORY-US-363: Trusted scope chain: the control plane gateway establishes tenant and project once from the validated token and forwards them to the service it fronts¶
enabling · persona platform-admin
As a platform administrator, I want the first Factory gateway to establish the tenant and the project of a call from the token and from nothing else, so that the service behind it receives a scope it can trust.
ADR-0015 decision 2 has every Factory contract carry the trusted tenant id and project id, derived from the authenticated context and never from prompt text or caller-controlled headers. The parts of that chain have owners. The scope type, the single scope accessor, the middleware and message filter that fill it and the names of the Factory token contract live in ConnectSoft.Extensions.AI.Factory.Abstractions and are delivered by AIFACTORY-US-220 of feature component-extensions-ai (AIFACTORY-TASK-186, AIFACTORY-TASK-142, AIFACTORY-TASK-1173). The validation rules of a generated platform gateway are AIFACTORY-US-237 of feature component-api-gateway-template, the service side is AIFACTORY-US-227 of feature component-base-template-factory-profile, and the token with its tenant claim, its role claims per project and its one audience is issued as feature component-auth-server-template-factory-tokens delivers it. This feature keeps the gateway side of the chain on the first real gateway, and this PBI configures it. It redefines no scope type, no claim name and no header name: it pins the packages. The repository ConnectSoft.AI.SoftwareFactory.ControlPlaneApi, created by the checklist of feature repository-and-pipeline-conventions, is configured with the authority of the Identity Platform, with its own audience, because a user token has one audience, the gateway that fronts its scopes, and with a fronts file. None of the seven services the gateway fronts exists in this increment, so a probe service generated by the Factory scaffold command stands behind it and the chain ends in a real accessor. On a call the gateway validates the token, takes the tenant from the tid claim, overwrites a tenant header the caller sent, admits the project the route addresses only when the token holds a role claim for that project or the tenant-wide Platform admin role, and forwards the tenant in the tenant headers of the SaaS tenancy libraries and the project in the project header the abstractions package names. The user token itself travels with the call: the amendment of ADR-0015 on the forwarded user token (decision D117) decides that a gateway forwards the user token to the service it fronts, that the service accepts the audience of its own gateway and that no token is exchanged between them. The gateway therefore forwards the token unchanged, requests no token exchange and issues no token of its own for a user call, and the probe service is configured with the authority of the Identity Platform and with the audience of the control plane gateway as the one audience it accepts: it validates the forwarded token itself and rejects a user token issued for the audience of another gateway. The probe service reads the scope from the accessor and returns it. The resolution of roles, source scope and policy override of a project through Projects.ResolveScope of ProjectService arrives with that service in increment I1 and is no part of this PBI: here the project right is what the role claims of the token grant. The gateway keeps no business state and no copy of a scope, and every refusal is a problem response that is logged with the correlation id and without token content.
Acceptance criteria
| AC1 | Given the control plane gateway generated with UseFactoryProfile and configured with the authority of the Identity Platform and its own audience, when a call with a valid user token of a member of a project passes it to the probe service, then the scope the probe service reads from the accessor of the pinned abstractions package holds the tenant of the tid claim and the project the route addresses, and both equal what the token grants (ADR-0015 decision 2, FR-01, descriptor execution-scope-v1). |
| AC2 | Given the same call with a tenant header and a project header that the caller typed with other values, when it passes the gateway, then the tenant header is overwritten with the claim of the token, the typed project is never read into the scope, and the probe service sees only the scope the token grants (ADR-0015 decision 2; docs/architecture/adr/0015-factory-tenancy-under-canonical-adr-0100.md). |
| AC3 | Given the gateway repository, when its architecture test inspects its references and types, then the scope type, the accessor, the claim type names and the project header name come from the pinned ConnectSoft.Extensions.AI.Factory.Abstractions, the tenant header names come from the SaaS tenancy libraries, the repository declares none of them, and the gateway owns no store beside the shared cache (ADR-0028 decisions 2 and 7; model/services/control-plane/ControlPlaneApi.yaml). |
| AC4 | Given a call with a valid user token that passed the gateway, when the probe service receives it, then the request carries the user token the caller sent, unchanged, the probe service validates it against the authority and accepts it because the one audience it accepts is the audience of the control plane gateway, the gateway requested no token exchange and issued no token of its own for the call, and a user token issued for the audience of another gateway that is sent to the probe service directly is rejected with 401 (ADR-0015 amendment on the forwarded user token; model/services/control-plane/ControlPlaneApi.yaml names the gateway and what it fronts). |
| Traces: descriptors | execution-scope-v1 |
| Traces: adrs | ADR-0015, ADR-0028 |
| Traces: requirements | FR-01 |
| Depends on | feature:component-extensions-ai, feature:component-api-gateway-template, feature:component-base-template-factory-profile, feature:component-auth-server-template-factory-tokens, feature:repository-and-pipeline-conventions |
| Sources | docs/architecture/adr/0015-factory-tenancy-under-canonical-adr-0100.md, docs/architecture/adr/0028-one-repository-and-deployable-per-service.md, docs/architecture/capability-dependencies.md, docs/reference/schemas/execution-scope.schema.json, model/services/control-plane/ControlPlaneApi.yaml, model/gateways.yaml |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-187 Gateway establishes the scope from the token and the project membership |
implementation | The control plane gateway, generated from the API gateway template with UseFactoryProfile, is configured with the authority of the Identity Platform, its own audience and a fronts file that routes to the probe service; it establishes the scope from the validated token (the tenant from the tid claim, the project from the role claims), forwards it in the tenant headers of the SaaS tenancy libraries and in the project header of the pinned Factory abstractions package, forwards the user token unchanged to the service it fronts without a token exchange, and answers every refusal with a problem response; the resolution through ProjectService is not part of this task and arrives in I1. |
ConnectSoft.AI.SoftwareFactory.ControlPlaneApi |
AIFACTORY-TASK-1515 Probe service and test token issuer in the acceptance suite of the gateway |
fixture | The acceptance suite of the gateway repository hosts a probe service generated by dotnet new connectsoft-base with UseFactoryProfile, with one read endpoint that returns the scope of the accessor, one resource by identifier in each of two tenants and one command that changes state and publishes an event; tokens are signed by the test issuer of the generated suite with the claim type names of the pinned Factory abstractions package; the probe service is configured with that issuer as its authority and with the audience of the control plane gateway as the one audience it accepts; the probe service uses a throwaway database of the pipeline container of the generated acceptance suite, and no named or shared database is touched. |
ConnectSoft.AI.SoftwareFactory.ControlPlaneApi |
AIFACTORY-TASK-1516 Verify the carried scope and the pinned definitions |
verification | Run dotnet test -c Release --filter Category=Acceptance on the gateway solution; the carried-scope test, the typed-header test, the forwarded-token test with its rejection of a token for another audience and the architecture test over the pinned packages pass and prove AC1 to AC4 of AIFACTORY-US-363 (ADR-0015, FR-01). |
ConnectSoft.AI.SoftwareFactory.ControlPlaneApi |
AIFACTORY-US-364: Trusted scope chain: the scope established at the edge travels in the run event envelope and the handler of another service reads the same tenant and project¶
enabling · persona platform-admin
As a platform administrator, I want the scope of a call to reach the handler of an event that the call caused, so that work done after the request ended is still attributed to the tenant and project of the caller.
A call does not end at the first service. ADR-0014 decision 1 makes the trusted tenant id required and the project id required where applicable in the port-level envelope of every Factory integration event; the schema requires the tenant and leaves the project optional. The amendment of the ADR on envelopes per event family settles which envelope that is: a Factory service writes the run event envelope of the contracts package, the descriptor run-event-envelope-v1, and AgentEventEnvelope of the Factory messaging library carries agent lifecycle events only. This PBI proves the second half of the chain across two processes, and only what the chain alone can prove. The two probe services are the output of the pinned base template: nothing of the generated outbox, inbox, tenant row filter, message filter or scope middleware is edited, and the probes add only the endpoint that returns the scope, the command that publishes one event and the handler that records the scope it read. The behaviours of that generated code are proven on the generated solution of the template and are not proven a second time here: the outbox record in the transaction of the command and the absence of an event after a rollback are the gate of AIFACTORY-US-226, and the refusal of an envelope without a tenant, the tenant-only scope of a tenant-level event and the refusal by a handler that declares itself project-scoped are AIFACTORY-US-227. What is left for the chain is the value. The probe service behind the gateway handles a command under a token of one tenant and project and publishes an event; the envelope takes tenantId and projectId from the scope accessor, never from the payload and never from a header. A second probe service consumes the event over the Orleans messaging profile, the message filter of the pinned abstractions package fills the accessor from the envelope, and the handler reads the same tenant and project that the token of the original call granted when it passed the gateway. The trace id of the envelope stays diagnostic and is never read as a scope. This PBI adds no envelope field, no filter and no scope type: the acceptance solution pins the published contracts package and the published abstractions package from the ConnectSoft feed, and an architecture test fails on a local copy of either. Each probe service uses a throwaway database of the pipeline container of the generated acceptance suite; no named or shared database is touched.
Acceptance criteria
| AC1 | Given the two probe services of the acceptance solution, when their generated files are compared with a fresh generation from the pinned base template package, then the generated outbox, inbox, tenant row filter, message filter and scope middleware are unchanged, the probes add only the scope endpoint, the publishing command and the recording handler, and the chain test asserts only the scope values end to end, because the outbox commit and the scope refusals of the generated service are gated by AIFACTORY-US-226 and AIFACTORY-US-227 of feature component-base-template-factory-profile (ADR-0014 decision 4; model/backlog/pbis/component-extensions/component-base-template-factory-profile.yaml). |
| AC2 | Given a command that reaches the first probe service through the gateway under a token of one tenant and project and publishes an event under run-event-envelope-v1, when the event is delivered to the second probe service and its handler runs, then the accessor returns the tenant and the project of the token of the original call that passed the gateway, read from the envelope and not from the payload, and the trace id of the envelope is not used as a scope (ADR-0014 decision 1, ADR-0015 decision 2). |
| AC3 | Given the acceptance solution of the gateway repository, when its architecture test runs, then the envelope type is the one of the pinned contracts package, the message filter and the accessor are those of the pinned abstractions package, both are restored from the ConnectSoft feed without a project reference, and the solution declares no envelope and no scope type of its own (ADR-0014 amendment on envelopes per event family; descriptor run-event-envelope-v1). |
| Traces: descriptors | run-event-envelope-v1, execution-scope-v1 |
| Traces: adrs | ADR-0014, ADR-0015 |
| Depends on | AIFACTORY-US-363, feature:contracts-package, feature:component-extensions-ai, feature:component-base-template-factory-profile |
| Sources | docs/architecture/adr/0014-run-and-lifecycle-envelopes.md, docs/architecture/adr/0015-factory-tenancy-under-canonical-adr-0100.md, docs/reference/event-envelope.md, docs/reference/schemas/run-event-envelope.schema.json, model/backlog/pbis/component-extensions/component-base-template-factory-profile.yaml |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-1517 Publishing command and consuming handler of the two probe services |
fixture | The probe service of AIFACTORY-TASK-1515 publishes one event from its command under the run event envelope of the pinned contracts package through the generated outbox, which is not edited; a second probe service, generated by the same scaffold command, consumes it over the Orleans messaging profile and records the scope its handler read from the accessor; each probe service uses a throwaway database of the pipeline container of the generated acceptance suite, created and dropped by the run, and no named or shared database is touched. | ConnectSoft.AI.SoftwareFactory.ControlPlaneApi |
AIFACTORY-TASK-1518 Pins of the contracts package and the abstractions package in the acceptance solution |
contract | The acceptance solution of the gateway repository pins the published versions of the contracts package and of ConnectSoft.Extensions.AI.Factory.Abstractions in its central package file, restores them from the ConnectSoft feed without a project reference, and an architecture test fails when the solution declares an envelope type, a scope type or a message filter of its own; a second test generates a service from the pinned base template package and fails when a generated file of a probe service differs from it. |
ConnectSoft.AI.SoftwareFactory.ControlPlaneApi |
AIFACTORY-TASK-1519 Verify the scope in the envelope and in the handler |
verification | Run dotnet test -c Release --filter Category=Acceptance on the gateway solution; the comparison of the probe services with the output of the pinned template, the scope the handler of the second process read and the architecture test pass and prove AC1 to AC3 of AIFACTORY-US-364 (ADR-0014, ADR-0015). |
ConnectSoft.AI.SoftwareFactory.ControlPlaneApi |
AIFACTORY-US-365: Trusted scope chain: the running gateway refuses a missing token or right with 401 or 403 before any service is called, and a resource of another tenant is answered 404 by the service¶
evidence · persona platform-admin
As a platform administrator, I want proof that every call the token does not grant gets the decided answer, from the running gateway or from the tenant filter of the service behind it, so that no service ever acts on a scope a caller merely claims.
This PBI is the proof of the feature and of the readiness demonstration that a request without scope is refused. The cases are run through a running control plane gateway with the running probe service behind it, not against a mock of either, and each one asserts two things: the answer, and what the probe service recorded. A call the gateway admits reaches the probe service with the user token of the caller, forwarded unchanged and accepted by the service for the audience of its gateway, with no token exchange between the two (ADR-0015 amendment on the forwarded user token, decision D117), which AIFACTORY-US-363 proves. The answers are the decided ones, and who gives them differs. The gateway refuses before any service is called. A call without a token, with an expired token, with an identity token or with a user token issued for the audience of another gateway is answered 401. A valid token that lacks the scope the operation names, or a route that addresses a project for which the token holds no role claim while the token is not Platform admin, is answered 403: a missing scope or right inside the tenant of the caller. For each of these the probe service records no call. A resource of another tenant has two cases with two owners. Case a: a route that addresses another tenant by its tenant identifier is answered 404 by the gateway and nothing is forwarded, as AIFACTORY-US-237 generates it. Case b: a request for a resource identifier that belongs to another tenant cannot be refused by the gateway, which owns no business state and cannot know the tenant of a resource identifier (ADR-0028 decisions 2 and 7). It is forwarded under the tenant of the caller, the tenant row filter of the probe service, which AIFACTORY-US-227 generates, finds no row, and the probe service answers 404 with the same body as an identifier that does not exist, over gRPC with the status NOT_FOUND, as the amendment of ADR-0015 decides (decisions D113 and D114). The response never confirms that the resource exists, and the probe service records exactly one call, under the tenant of the caller. A tenant header typed by the caller is overwritten and never decides anything. A workload token carries service scopes, no audience of a user API and no tenant claim: it is admitted only on a route whose operation names an svc. scope the token holds, and the tenant and project it forwards are read only under that scope. When the authority of the Identity Platform cannot be reached, the gateway fails closed: tokens whose signing keys are cached validate until they expire and every other call is refused, as the failure mode of the gateway in the model states. Every refusal is counted for its route and logged with the correlation id and without token content. The matrix feature and the test issuer are the ones the pinned API gateway template generated; they are kept unchanged, and this PBI adds only the rows the template cannot hold. The run of the matrix in the pipeline of the gateway repository is the evidence.
Acceptance criteria
| AC1 | Given the running gateway and probe service, when a call arrives without a token, with an expired token, with an identity token or with a user token whose audience is another gateway, then the answer is 401 and the probe service records no call (ADR-0015 amendment on the one audience of a user token; ADR-0028 decision 2). |
| AC2 | Given a valid user token, when the token lacks the scope the operation names, or the route addresses a project for which the token holds no role claim and the token is not Platform admin, then the answer is 403, a tenant or project header typed by the caller changes nothing, and the probe service records no call (ADR-0015 decisions 2 and 3, FR-01). |
| AC3 | Given two tenants with one resource each in the probe service, when a caller of the first tenant addresses the second tenant by its tenant identifier in a route, then the gateway answers 404, over gRPC NOT_FOUND, and the probe service records no call; and when the caller requests the identifier of the resource of the second tenant over REST and over gRPC, then the call is forwarded under the tenant of the caller, the tenant row filter of the probe service finds no row, the probe service answers 404 with the same body as for an identifier that does not exist, over gRPC the status NOT_FOUND, the probe service records one call under the tenant of the caller, and the response does not confirm that the resource exists (ADR-0015 amendment on a resource of another tenant; ADR-0028 decisions 2 and 7; docs/architecture/adr/0015-factory-tenancy-under-canonical-adr-0100.md). |
| AC4 | Given a workload token, which carries service scopes, no audience of a user API and no tenant claim, when it calls a route whose operation names an svc. scope it holds, then the call is admitted and the forwarded tenant and project are read under that scope; when it calls any other route, or forwards a tenant without holding the scope, then the call is refused and the probe service records no call (ADR-0015 amendment on the workload token; descriptor execution-scope-v1). |
| AC5 | Given the authority of the Identity Platform is unreachable, when calls arrive, then a token whose signing key is cached validates until it expires, every other call is refused, the health of the gateway reports the authority, and each refusal of the matrix is counted for its route and logged with the correlation id and without token content (ADR-0028 decision 7; model/services/control-plane/ControlPlaneApi.yaml lists the failure mode). |
| Traces: descriptors | execution-scope-v1 |
| Traces: adrs | ADR-0015, ADR-0028 |
| Traces: requirements | FR-01 |
| Depends on | AIFACTORY-US-363, feature:component-api-gateway-template, feature:component-base-template-factory-profile, feature:component-auth-server-template-factory-tokens |
| Sources | docs/architecture/adr/0015-factory-tenancy-under-canonical-adr-0100.md, docs/architecture/adr/0028-one-repository-and-deployable-per-service.md, model/services/control-plane/ControlPlaneApi.yaml, model/backlog/increments.yaml |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-1520 Rows added to the generated refusal matrix for the running probe service, the foreign tenant and the unreachable authority |
fixture | The matrix feature and the test issuer that the pinned API gateway template generated (third task of AIFACTORY-US-237) are kept unchanged in the acceptance suite of the gateway repository; this task adds only the rows the template cannot hold: the running probe service in place of the fake fronted service with the recorded-call expectation (no recorded call for 401, for 403 and for a route that addresses another tenant by its tenant identifier; one recorded call under the tenant of the caller for 200 and for a resource identifier of another tenant, which the probe service answers 404 or NOT_FOUND), the resource of another tenant over REST and gRPC, and the unreachable authority with a cached and an uncached signing key; a gap found in the generated matrix is reported to feature component-api-gateway-template and not patched here. |
ConnectSoft.AI.SoftwareFactory.ControlPlaneApi |
AIFACTORY-TASK-143 Refusal tests for missing and forged scope |
verification | Acceptance tests through the running gateway prove that a call without a token, a call with a scope or a project the token does not grant and a call with a typed tenant or project header are refused with 401 or 403 and reach no service, which proves AC1 and AC2 of AIFACTORY-US-365 (ADR-0015, FR-01). | ConnectSoft.AI.SoftwareFactory.ControlPlaneApi |
AIFACTORY-TASK-1521 Verify the foreign tenant, the workload token and the unreachable authority |
verification | Run the generated matrix with the rows of AIFACTORY-TASK-1520 in the pipeline of the gateway repository; the row for a route that addresses another tenant answers 404 from the gateway with no recorded call, the rows for a resource identifier of another tenant over REST and gRPC answer 404 and NOT_FOUND from the probe service with one recorded call under the tenant of the caller, and the rows for the workload token with and without its svc. scope and for the unreachable authority answer as stated, with the refusal counter and the log line asserted, which proves AC3 to AC5 of AIFACTORY-US-365 (ADR-0015, ADR-0028). |
ConnectSoft.AI.SoftwareFactory.ControlPlaneApi |
AIFACTORY-US-001: A call carries a trusted scope from the edge to a service¶
enabling · persona platform-admin
As a platform administrator, I want every call to carry a tenant and project scope that was established once from the token of the caller, so that no service ever acts on a scope a caller merely claims.
This is the integration PBI of the feature. A platform administrator sees one call chain carry a trusted scope from the edge to a service and on into an event handler, which is the second demonstration of increment I0. The scope type, the accessor with its middleware and the Factory token contract names are not defined here: they live in ConnectSoft.Extensions.AI.Factory.Abstractions and are delivered by AIFACTORY-US-220 of feature component-extensions-ai, which this PBI depends on. The feature keeps the gateway side and its refusal tests. AIFACTORY-US-363 configures the control plane gateway so that it establishes tenant and project once from the validated token and forwards them together with the user token itself, which the fronted service accepts for the audience of its gateway, with no token exchange between the two (ADR-0015 amendment on the forwarded user token, decision D117); AIFACTORY-US-364 carries the scope in the run event envelope of the contracts package to the handler of a second service; AIFACTORY-US-365 proves through the running gateway that a call the token does not grant is answered 401 or, inside the tenant of the caller, 403 before any service is called, and that a resource of another tenant is answered 404, NOT_FOUND over gRPC, by the tenant row filter of the service, which is called under the tenant of the caller and finds no row. Those three PBIs sign their tokens with the test issuer of the generated suite. What this PBI adds is the real issuer. The acceptance stage of the repository ConnectSoft.AI.SoftwareFactory.ControlPlaneApi starts a local authorization server generated from connectsoft-authorization-server at the version the gate of feature component-auth-server-template-factory-tokens published, with one registered client, one tenant, one project and one member, and runs one carried call and one refused call with tokens of that server through the gateway, a probe service and its consumer. The matrix of refusals stays with AIFACTORY-US-365 and is not repeated here. The seven services the gateway fronts arrive from increment I1 on and take the chain as it is proven here; the resolution of roles, source scope and policy override through ProjectService arrives with that service and adds to the chain without changing who establishes the scope.
Acceptance criteria
| AC1 | Given a valid token of the local authorization server with membership in a project, when a request passes the gateway, then the service reads tenant and project from the scope accessor and they equal those of the token, and the service received that user token forwarded by the gateway and accepted it for the audience of its gateway (ADR-0015 decision 2 and its amendment on the forwarded user token, FR-01, descriptor execution-scope-v1). |
| AC2 | Given a request without a token or with a project the token does not grant, when it reaches the gateway, then it is refused with 401 or 403 and no service is called, and a request for a resource identifier of another tenant is answered 404, over gRPC NOT_FOUND, by the service, which is called under the tenant of the caller and finds no row (ADR-0015 decision 3 and its amendment on a resource of another tenant). |
| AC3 | Given a service publishes an event, when another service handles it, then the handler sees the same tenant and project in the envelope run-event-envelope-v1 and reads them from the scope accessor (ADR-0014 decision 1). |
| Traces: descriptors | execution-scope-v1, run-event-envelope-v1 |
| Traces: adrs | ADR-0015, ADR-0014 |
| Traces: requirements | FR-01 |
| Depends on | AIFACTORY-US-363, AIFACTORY-US-364, AIFACTORY-US-365, feature:component-extensions-ai, feature:component-auth-server-template-factory-tokens |
| Sources | docs/architecture/capability-dependencies.md, docs/ai-software-factory/current-state.md, docs/architecture/adr/0015-factory-tenancy-under-canonical-adr-0100.md, model/backlog/increments.yaml |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-1566 Local authorization server of the acceptance stage with one client, tenant, project and member |
fixture | The acceptance stage of the gateway repository generates a local authorization server from connectsoft-authorization-server at the version the gate of feature component-auth-server-template-factory-tokens published, into a working folder of the pipeline that is not committed, and starts it with one registered client, one tenant, one project and one member whose token carries the tenant claim and a role claim for the project; the generated output is used unchanged, its clients work only in Development (AIFACTORY-US-245), its store is a throwaway database of the pipeline container, and no named or shared database is touched. |
ConnectSoft.AI.SoftwareFactory.ControlPlaneApi |
AIFACTORY-TASK-188 Acceptance tests for a carried and a refused scope with tokens of the authorization server |
verification | Two acceptance tests of one chain pass in the pipeline of the gateway repository with tokens of the local authorization server of AIFACTORY-TASK-1566: one carried call, whose scope travels from the token through the gateway and the probe service into the handler of its consumer and whose user token the probe service receives forwarded and accepts for the audience of the gateway, and one refused call for a project the token does not grant, which is answered 403 and reaches no service; the matrix of refusals stays with AIFACTORY-US-365 and is not repeated here, which proves AC1 to AC3 of AIFACTORY-US-001 together with the matrix run of AIFACTORY-TASK-1521. | ConnectSoft.AI.SoftwareFactory.ControlPlaneApi |
AIFACTORY-TASK-718 Verify scope-end-to-end by running the declared command |
verification | Run dotnet test -c Release --filter Category=Acceptance; it passes and proves AC1 to AC3 of AIFACTORY-US-001. |
ConnectSoft.AI.SoftwareFactory.ControlPlaneApi |