Agenda

Demonstration of current work
Review the roadmap
Design Questions

Demonstration

Planned Architecture

Working Client Management and Authentication

sequenceDiagram
    actor Sys Admin

    rect rgb(191, 223, 255)
    note right of Sys Admin: One time setup.

        Sys Admin->>Config Service: POST /connect/register
        Config Service->>Identity Provider: Create credentials
        note right of Identity Provider: Created with config role
        
        Config Service-->>Sys Admin: clientCredentials
    end

    Sys Admin->>Config Service: POST /v2/vendors
    Config Service->>Config Database: INSERT dbo.Vendor

    Sys Admin->>Config Service: POST /v2/applications

    Config Service->>Identity Provider: Create credentials
    note right of Identity Provider: Created with dms role
    Identity Provider-->>Config Service: clientCredentials
    Config Service->>Config Database: INSERT dbo.Application
    Config Database -->>Config Service: applicationId
    Config Service->>Config Database: INSERT dbo.ApplicationEducationOrganization
    Config Service->>Config Database: INSERT dbo.ApiClient

    Config Service-->>Sys Admin: clientCredentials

Roadmap

Getting to a pilot-ready release candidate by Tech Congress was always going to be challenging. The team has been working hard, but we need to adjust the milestones and expectations for release candidate 1.

Goals for release candidate are broadly:

Deployable and fully functional in the basic CRUD operations on all Resources and Descriptors.
Proper error handling and edge case management.
Performance on par with the ODS/API.
Be useable for basic field testing and non-critical path use cases.

While we want to be looking ahead to supporting state agency use, at the 2024 Summit we agreed to prioritize service provider / LEA usage scenarios first. Given that,

Milestone	Functional Goals
0.1	Compliant Discovery API, Descriptor API, and Resource API definition (except GET by query): able to run bulk upload, smoke test. Includes JSON validation based on API schema file. Fake OAuth (1).
0.2	📢 Milestone 0.2.0 has been reached! .NET application with PostgreSQL storage Level 0 and Level 1 document validation Reference and descriptor validation Error message like ODS/API 7.2 Docker and Kubernetes
0.3	Streaming data out via Kafka GET by query using OpenSearch Cascading updates on allowed key changes Abandoned direct Kubernetes support as too costly by 10/1 (Ed-Fi Summit)
0.4	Token authorization Client credentials management Namespace authorization BONUS: Elasticsearch/Kibana instead of OpenSearch/OpenSearch Dashboard
0.5	Design spikes around ed-org authorization Concurrency management with eTags Extensions Multiple data standards (DS 5.2)
0.6	Dynamic profiles Multitenancy and routing
0.7	Education organization authorization Claimset customization

note

Items for future scope beyond this include: Change Queries, using PostgreSQL for queries instead of OpenSearch / Elasticsearch, real-time level 2 validation using Kafka, identity API, etc.

Design Questions

What plans are there for error detection (i.e. dropped records) and correction?

A question that arose at the Ed-Fi Summit session. Suggestions?

How will year rollover be handled?

Perhaps not germane to the release candidate, but we should still ask: are there special considerations that the development team needs to be thinking about in advance?