Skip to:

Skip to Jira Navigation
Skip to Side Navigation
Skip to Main Content

Eureka - Investigations and Designs - Trillium R2 2025

Description

Scope:

Investigate migration paths from permissions → capabilities/roles
TBD

Priority

P3

Labels

SolutionArchitectureback-endepam-eurekafront-end

Fix versions

Trillium (R2 2025)

Development Team

Eureka

Assignee

Craig McNally

Solution Architect

None

Parent

None

Parent Field Value

None

Parent Status

None

Linked work items

clones

Investigations and Designs - Sunflower R1 2025

continues

Investigations and Designs - Phase 6

is defined by

Spike - Load shared assets: sounds

Spike - Load a remote app with conflicting peer-deps

PLACEHOLDER - Spike - investigate improvements to impersonation

Investigate options cluster-wide health checks

Investigate solutions for mapping SSO claims to capabilities

Design solution for AuthUser -> User demotion

Spike - Investigate migration paths from permissions -> capabilities/roles

Spike - Revisit the use of system tokens for module-to-module calls

Spike - Revisit Policies

PLACEHOLDER - Spike - Investigate Kong advanced features

PLACEHOLDER - Spike/PoC - Investigate the ability to resume jobs in the event that the node which was handling the job fails

PLACEHOLDER - How to organize/refactor Karate Tests for Applications

Spike - Validate that upgrade of application does not affect other installed applications

Measure sidecar resource consumption w/ native binaries

Spike - Explore options for moving password-reset logic out of mod-users-keycloak, into mod-roles-keycloak

Spike - Improved handling of capabilities for permissionsDesired

Spike - Investigate options for m2m calls based on defined module permissions

Spike - Cascade disable based on dependencies

Spike - automatically enable applications based on dependencies

Spike - Investigate the possibility to remove kafka from the sidecars

Spike - Investigate options for loading sample/reference data w/ finer granularity

Spike - Improved handling of reference data during upgrades

SPIKE: Review Permission Replaces for Upgrades

Spike - Design improved handling of updating capability placeholders when an application is enabled

Spike - Design long term solution for system user cross-tenant m2m requests

Spike - How to provide greater insight into asynchronous entitlement progress

Spike - investigate how to protect ALL mgr-* endpoints for cross-tenant requests

Spike - Investigate Kong scalability - Upper bound for # of tenants?

Spike - investigate the impact of optional application dependencies on mgr-* / entitlement flow

Spike - Define implementation/approach for async mgr-tenant-entitlements feedback loop

Spike - Investigate TLS w/o FIPS

Checklist

hide

Activity

Show:

Resize issue view side panel

Details
Reporter
Craig McNally
PO Rank
0
Back End Estimator
Oleksii Kuzminov
Release
Trillium (R2 2025)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs

Created January 21, 2025 at 11:12 PM

Updated April 11, 2025 at 7:15 PM

TestRail: Cases

TestRail: Runs