IUA FT Evaluation: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 43: Line 43:


* '''Have all open issues listed in the Supplement been closed?'''
* '''Have all open issues listed in the Supplement been closed?'''
<span style="color:blue">'''[TO VERIFY]'''</span> Not checked against the "open issues" section of TI Rev 2.5.
<span style="color:blue">'''[DISCUSS]'''</span> No. The TI Rev 2.5 lists three open issues: Issue 12 (AuditEvent for Resource Server DENY decisions), Issue 14 (possible future use of OAuth Rich Authorization Requests, <code>authorization_details</code>), and Issue 15 (the OAuth 2.1 draft version cited, draft-09 in ITI-71 but draft-01 in ITI-72 and ITI-102). Source: [https://profiles.ihe.net/ITI/IUA/index.html profiles.ihe.net IUA]. Issue 15 is an editorial inconsistency that should be fixed before Final Text. Issues 12 and 14 need a TC decision on whether they are significant.


* '''Have all significant issues at Connectathon been dealt with?'''
* '''Have all significant issues at Connectathon been dealt with?'''
Line 249: Line 249:
# Integrate CP-ITI-1324 and CP-ITI-1331 into the IUA text and republish.
# Integrate CP-ITI-1324 and CP-ITI-1331 into the IUA text and republish.
# Re-run or confirm Connectathon coverage against the changed IUA text (especially the client authentication change in CP 1331).
# Re-run or confirm Connectathon coverage against the changed IUA text (especially the client authentication change in CP 1331).
# Confirm the TI "open issues" section is empty or closed.
# Resolve or close TI open Issues 12, 14 and 15 (see the open-issues item above).
# Confirm the comment record for TI Rev 2.5 has no unresolved significant comments.
# Confirm the comment record for TI Rev 2.5 has no unresolved significant comments.
# Confirm the option list and Gazelle coverage.
# Confirm the option list and Gazelle coverage.
Line 256: Line 256:
# Draft the one-page profile overview.
# Draft the one-page profile overview.
# Verify the deployment entries (Canada, NEN 7541, UK).
# Verify the deployment entries (Canada, NEN 7541, UK).
# Fix editorial errors before Final Text: MHD Volume 2 section 3.66.5.2 says "Get Access Token [ITI-72]" where it should say ITI-71; the OAuth 2.1 draft is cited as draft-09 in 3.71.3 and as draft-01 in 3.72.3 and 3.102.3 (Issue 15).
# Confirm the master-branch changes (the "Bearer" option that replaces Token Introspection, per the GitHub README) are either included in the next TI or dropped before Final Text. Rev 2.5 still lists Token Introspection.


== Sources ==
== Sources ==

Latest revision as of 10:42, 19 November 2026

IUA FT Evaluation

Internet User Authorization (IUA) - Final Text Assessment - DRAFT

Intro: Internet User Authorization (IUA) has been nominated for advancement to Final Text (Advocate: Steven Nichols). Items in blue text warrant Committee discussion under the Final Text Process.

Profile Internet User Authorization (IUA)
Domain IT Infrastructure (ITI)
Current status Trial Implementation, Revision 2.5 (dated 2026-06-18)
Year introduced ~2015 (approximate)
Prepared [date]

Proposal

The page opens with the nomination above. It has no checklist items of its own.

Technical Committee Checklist

  • Are all significant CPs against the profile "closed"?

[DISCUSS] Partly. No IUA CP is Assigned. Two IUA CPs passed ballot but are not yet in the published text:

    • CP-ITI-1331 (Drop client_id, client_secret authentication requirement), Completed, ballot-67, last updated 2026-07-14. This is a normative change. It removes the mandated client_secret/HTTP Basic requirement for the Client Credentials grant and for confidential clients, and it changes the token_endpoint_auth_methods_supported text. It is dated after TI Rev 2.5, so the change is not in the current TI.
    • CP-ITI-1324 (ITI-71: clarify that the JWT signature is supported or required), Completed, ballot-66, last updated 2026-03-25. It resolves an ambiguity about whether JWT tokens must be signed. Pub2026 lists it as "Ready".

Closed CPs: CP 1255 (Final Text, merged Pub2025), CP 1256 (Integrated 2022), CP 1257 (Cancelled, merged into 1256), CP 1288 (Integrated 2023), CP 1148 (Integrated 2019). Recommendation: integrate CP 1324 and CP 1331 into the next IUA publication, then re-confirm the profile has no significant open CPs.

  • Are all significant CPs against the underlying standards "closed"?

[TO VERIFY] No IUA-specific standards CP was found. CP 1285 (XUA, Audience SAML errata) is Integrated in 2024 and belongs to XUA. CP 1287 (XUA canonicalization) is Assigned and belongs to XUA. Check whether OAuth 2.1 or RFC 7523 / 8707 / 8693 errata affect IUA.

  • Have all significant comments been CP'd or rejected?

[TO VERIFY] Not checked against the ballot comment record for TI Rev 2.5.

  • Have all open issues listed in the Supplement been closed?

[DISCUSS] No. The TI Rev 2.5 lists three open issues: Issue 12 (AuditEvent for Resource Server DENY decisions), Issue 14 (possible future use of OAuth Rich Authorization Requests, authorization_details), and Issue 15 (the OAuth 2.1 draft version cited, draft-09 in ITI-71 but draft-01 in ITI-72 and ITI-102). Source: profiles.ihe.net IUA. Issue 15 is an editorial inconsistency that should be fixed before Final Text. Issues 12 and 14 need a TC decision on whether they are significant.

  • Have all significant issues at Connectathon been dealt with?

[TO VERIFY] Not checked. CP 1331 was submitted from a Connectathon-related implementation (client_secret in the HTTP header considered insecure; private_key_jwt used instead). The Connectathon issue log for 2024-2026 should be reviewed.

  • Has the Connectathon Project Manager been queried and significant issues addressed?

[TO DO] Not done.

Technical Committee Consensus

  • [date]: [TC decision and minutes reference]. Pending the Technical Committee checklist above.

Planning Committee Checklist

  • Has the profile been through a Connectathon in at least two regions?

Yes. Europe (2022-2026) and Japan (2024). North America (2016-2020) is historical.

Connectathon results, IUA by company and event (source: CAT results 2026.xlsx). Actors: AC = Authorization Client, AS = Authorization Server, RS = Resource Server.

Company Eur./NA 2022 Eur. 2024 Eur. 2025 Eur. 2026 Japan 2024
A-thon srl (actor n/a) AC, AS, RS AC, AS, RS
Bastion 365 AS, RS AS
Dedalus SpA AC
EYONE AC
Fluint Health GmbH AC
Founda Health RS RS
Foundation for Research and Technology-Hellas AS, RS
GPI SPA AS, RS
Gnomon Informatics SA AS, RS
InterSystems Corporation AC, AS, RS
IRM, Inc. (actor n/a)
Lyniate (actor n/a)
Sorsix Pty Ltd AC, AS, RS
Systelab Technologies S.A. AC AC AC
Telerad Tech Pvt Ltd AS, RS
UniDoc S.r.l. AC
VISUAPPS AC, AS, RS AC, AS, RS AC, AS, RS
synedra information technologies GmbH AC AC, RS AC, RS
Intersystems Japan AC
Morita Manufacturing AC
Totals (vendors per event) 3 7 (EU) + 2 (JP) 10 8 (included above)

Note: the 2022 EU_NA and 2023 EU tabs use a matrix layout that does not record actors. Their vendor names are used only where listed. The 2023 EU tab (4 vendors) has blank vendor headers in the export and is not in the table.

  • Has the profile been successfully tested with all actors at least at one Connectathon?

Yes. AC, AS and RS are each tested by 4 or more vendors in each of 2024, 2025 and 2026.

  • Have different implementations of each actor in the profile been tested?

Yes. 2024-2026 has 18 distinct vendors overall (CAT Summary sheet: 18 for 2022-26).

  • Have all the options been tested successfully at at least one Connectathon?

[TO VERIFY] The CAT data is recorded at actor level and does not show option-level results. Confirm the IUA option list (e.g., JWT, client credentials) against the Connectathon records.

  • Are there IHE-provided software testing tools to address all aspects of the profile?

[TO VERIFY] Confirm Gazelle test coverage for IUA actors and the CP 1331 change (client authentication methods).

  • Have the standards underlying the profile been implemented? In similar use cases? In healthcare? In general IT?

Yes. IUA uses OAuth 2.0 / 2.1, JWT (RFC 7519), JWS (RFC 7515), JWE, and related RFCs (7523, 8693, 8707), which are widely deployed in general IT and in health-sector identity systems.

  • (Do you have concrete reason to believe that this works robustly in the Real World) / (Are any products available for purchase that implement the profile?)

Yes. Deployments listed in the earlier review: Canada Infoway pan-Canadian Projectathon (CT, ATNA, MHD, IUA, XDS, PIX); NEN 7541 Netherlands (MHD + IUA, WADO-RS); UK National Imaging Registry roadmap (MHDS, which includes IUA). 18 vendors have passed IUA testing in 2024-2026, which indicates commercial products. [VERIFY] the Canada and NEN 7541 entries against primary sources.

  • Have all issues that may have been raised about the profile been resolved?

[DISCUSS] No. CP 1331 (passed ballot-67) changes normative client authentication text. CP 1324 (ballot-66) clarifies JWT signing. Both are not yet in published text, and Connectathon testing in 2024-2026 was against the pre-change text. Also note CP 1248 (MHDS, "Adapt MHDS to actor scopes agreed upon in the IUA revision") is Assigned. It is an MHDS change that depends on IUA, and it does not block IUA.

  • Has there been sufficient interest in the profile to generate a one-page overview of the profile?

[TO DO] Not started. The existing IUA wiki page (Internet User Authorization) is a stub with a one-line description and links to the specification, and it can serve as the basis for the one-page overview. A proposed update is in IUA-wiki-page-update-proposal.txt in this folder.

Open items before Final Text is proposed

  1. Integrate CP-ITI-1324 and CP-ITI-1331 into the IUA text and republish.
  2. Re-run or confirm Connectathon coverage against the changed IUA text (especially the client authentication change in CP 1331).
  3. Resolve or close TI open Issues 12, 14 and 15 (see the open-issues item above).
  4. Confirm the comment record for TI Rev 2.5 has no unresolved significant comments.
  5. Confirm the option list and Gazelle coverage.
  6. Get implementer feedback through the domain secretary.
  7. Consult the Connectathon Project Manager.
  8. Draft the one-page profile overview.
  9. Verify the deployment entries (Canada, NEN 7541, UK).
  10. Fix editorial errors before Final Text: MHD Volume 2 section 3.66.5.2 says "Get Access Token [ITI-72]" where it should say ITI-71; the OAuth 2.1 draft is cited as draft-09 in 3.71.3 and as draft-01 in 3.72.3 and 3.102.3 (Issue 15).
  11. Confirm the master-branch changes (the "Bearer" option that replaces Token Introspection, per the GitHub README) are either included in the next TI or dropped before Final Text. Rev 2.5 still lists Token Introspection.

Sources

  • CAT results 2026.xlsx (Connectathon results, 2011-2026, Summary and year tabs)
  • IHE IT Infrastructure CP Tracking(1).xlsx (CP status: Active CPs, Pub2026, Pub2025)
  • CP-ITI-1324-01.docx (JWT signature, Completed, 2026-03-25)
  • CP-ITI-1331-02.docx (Drop client_id/client_secret requirement, Completed, 2026-07-14)
  • IHE ITI TF / IUA Trial Implementation Rev 2.5 (profiles.ihe.net)
  • IHE Final Text Process
  • REM-NM FT Evaluation (used as the template)