Skip to content

Milestones

List view

  • IAM for EOSC

    AARC guidelines implementation: G025, G061 and G031 principally.

    Due by June 30, 2026
    •2/7 issues closed
    28% complete5 open2 closed

  • Minimal SAS for EPIC

    First implementation of INDIGO IAM based on Spring Authorization Server framework

    Due by June 30, 2026
    •0/7 issues closed
    0% complete7 open0 closed

  • OpenID Federation

    By leveraging the trust infrastructure defined in the OpenID Federation specification, INDIGO IAM will be able to dynamically establish trust between providers, facilitate secure interactions using Trust Anchors to validate membership and compliance and eliminate the need for manual or bilateral trust agreements, simplifying integration and scaling.

    Due by May 31, 2026
    •4/7 issues closed
    57% complete3 open4 closed

  • IAM hardening

    Tasks related: No Access Tokens in DB, Hash client secrets, Complete MFA, Collect feedback on MFA, MFA fully in production, Improve logging/auditing, Bind access tokens to client (optional)

    Overdue by 19 day(s)
    •
    Due by January 30, 2026
    •14/17 issues closed
    82% complete3 open14 closed

  • General backlog

    IAM issues not yet scheduled for a release

    No due date
    •23/42 issues closed
    54% complete19 open23 closed