Commit 23c2f509 authored by Dimitrios Gogos's avatar Dimitrios Gogos
Browse files

docs: update timestamps in implementation, overview, and requirements...

docs: update timestamps in implementation, overview, and requirements documents to reflect the latest release date
parent 079643be
Loading
Loading
Loading
Loading
+4 −2
Changes for portal/implementation-and-delivery.md: 4 added lines, 2 removed lines.
Original line number Diff line number Diff line
@@ -3,7 +3,7 @@ type: Implementation & Delivery
title: "Portal — Implementation & Delivery"
description: "How the portal code is laid out, its settings, how it is built and deployed, what it logs, how it is tested, the known gaps of Release 2, and what comes in the next release and how."
tags: [portal, implementation, delivery]
timestamp: 2026-10-08T00:00:00Z
timestamp: 2026-10-20T00:00:00Z
component: Portal
version: "2.0"
status: "ETSI SDG OOP"
@@ -169,7 +169,9 @@ already in place.

### U.6 No-access state and "Your API products"

- **Missing.** A page for a product the user does not hold shows OEG's error.
- **Done.** Edge Application Management's Explore pages say when the user does not hold the
  API's product, instead of showing OEG's error.
- **Missing.** "Try it" still shows OEG's error, and there is no "Your API products" page.

### U.7 Quality on Demand and Traffic Influence pages

+5 −3
Changes for portal/overview-and-architecture.md: 5 added lines, 3 removed lines.
Original line number Diff line number Diff line
@@ -3,7 +3,7 @@ type: Architecture Spec
title: "Portal — Overview & Architecture"
description: "What the OOP Portal is and is not, the backend that acts for the browser, who sees which page, the portal's boundaries with OEG, Keycloak and AI², and open questions."
tags: [portal, bff, architecture]
timestamp: 2026-10-07T00:00:00Z
timestamp: 2026-10-20T00:00:00Z
component: Portal
version: "2.0"
status: "ETSI SDG OOP — first specification of a component already in use"
@@ -100,7 +100,9 @@ Roles add up: a user sees every page any of their roles allows. Operators keep t
| Federation, and the federation API in the catalog | `operator` |

What a call may actually do is OEG's decision. A user without the `edge-application-management`
product sees the Edge Application Management pages, but OEG refuses their calls.
product still sees the Edge Application Management overview, but the Explore pages tell them
their account cannot use the API yet instead of making calls OEG would refuse. That check only
shapes what the app shows; OEG still decides every call.

`platform-admin` has no page yet: user administration comes in the next release
([implementation-and-delivery.md §U](/portal/implementation-and-delivery.md)).
@@ -130,7 +132,7 @@ Platform-wide terms: [platform/glossary.md](/platform/glossary.md).
| UC-PORTAL-02 | Browse the API catalog, read each API's guide, try its operations in the browser | Everyone |
| UC-PORTAL-03 | Onboard application profiles, start and stop instances, deploy to edge cloud zones, list zones | Everyone, as far as OEG allows |
| UC-PORTAL-04 | Create and delete API clients for the products they hold; see the secret once | `app-provider` |
| UC-PORTAL-05 | Register and update partner operators, create and end federations, subscribe to partner zones | `operator` |
| UC-PORTAL-05 | Register and update partner operators, create and end federations, subscribe to partner zones, grant a partner zones and terms through its agreement | `operator` |
| UC-PORTAL-06 | Ask the AI² agent to do things on the platform | Everyone |
| UC-PORTAL-07 | See their own account: username, email, organization, roles | Everyone |

+5 −2
Changes for portal/requirements-and-design.md: 5 added lines, 2 removed lines.
Original line number Diff line number Diff line
@@ -3,7 +3,7 @@ type: Requirements & Design
title: "Portal — Requirements & Design"
description: "Portal requirements, the backend's routes, how login and sessions work, how calls reach OEG and AI², how API clients are created and deleted and what the portal does not keep in sync, the portal's tables, and its errors."
tags: [portal, bff, keycloak, api-clients, requirements]
timestamp: 2026-10-08T00:00:00Z
timestamp: 2026-10-20T00:00:00Z
component: Portal
version: "2.0"
status: "ETSI SDG OOP"
@@ -140,7 +140,10 @@ another site cannot trigger it.
The app uses this route for the catalog (`/api/oeg/openapi.json`), for "try it" (Swagger
requests are rewritten to go through it), for Edge Application Management
(`/edge-application-management/v0.1alpha1/...`) and for the Federation tab
(`/platform/v1/federation/...`).
(`/platform/v1/federation/...`): partners, their federations and zones, `/identity` for the
create-federation form, and `/agreements[/{agreementId}]` with `/local-zones` to grant a partner
zones and terms. A partner's agreement is read inside `GET /partners/{partnerOpId}`
([oeg/interface-contract.md §N.7](/oeg/interface-contract.md)).

**AI².** `POST /api/ai2/chat` goes to `AI2__CHAT_URL` with the same token and the body unchanged
(`{query, session_id}`). The same `401`, `502` and `504` rules apply. The list of conversations