...
Demonstration of current work
Review the roadmap
Design Questions
Demonstration
Configuration Service
Claimset management
Authentication
Keycloak
show start to finish initial setup and client creation
Roadmap
...
What is actually critical for release candidate?
etag, profile, multitenancy & routing
multiple authorization strategies
ownership based auth
can we do just relationship & namespace based authorization?
DS 5.2
call out that IIS / Powershell scripted route will not be ready
...
Planned Architecture
...
Working Client Management and Authentication
...
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
|
| ||||||||||||||||||||||||||||||
0.3
|
| ||||||||||||||||||||||||||||||
0.4
|
| ||||||||||||||||||||||||||||||
0.5 |
| ||||||||||||||||||||||||||||||
0.6 |
| ||||||||||||||||||||||||||||||
0.7 |
|
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?
...
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?