Internet User Authorization: Difference between revisions
JohnMoehrke (talk | contribs) |
Stevenichols (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
PROPOSED UPDATE to https://wiki.ihe.net/index.php/Internet_User_Authorization | |||
Wiki markup. Not yet posted. Items in [CONFIRM] need checking before posting. | |||
----- BEGIN WIKI MARKUP ----- | |||
= | = Internet User Authorization (IUA) = | ||
'''Internet User Authorization (IUA)''' is an IHE IT Infrastructure profile that conveys the identity, attributes and authorizations of a user to a RESTful service. It supports the authorization of transactions made over IHE's HTTP RESTful transports. IUA is the RESTful counterpart of [[XUA]] (Cross-Enterprise User Assertion), which uses SAML assertions. | |||
{| class="wikitable" | |||
|- | |||
! Status | |||
| Trial Implementation, Revision 2.5 (dated 2026-06-18) | |||
|- | |||
! Domain | |||
| IT Infrastructure (ITI) | |||
|- | |||
! Technology | |||
| OAuth 2.0 / 2.1 with JSON Web Tokens (JWT); HTTP RESTful transactions | |||
|- | |||
! Specification | |||
| [https://profiles.ihe.net/ITI/TF/Volume1/ch-34.html IUA Volume 1, Chapter 34] | |||
|} | |||
== Overview == | |||
IUA defines how a client application obtains an access token from an authorization server and presents it to a resource server. The resource server can then check the user's identity and authorizations before it processes a request. | |||
== Actors == | |||
* '''Authorization Client''': requests an access token for a user or client application. | |||
* '''Authorization Server''': issues access tokens after authenticating the client. | |||
* '''Resource Server''': accepts access tokens and enforces authorization on requests. | |||
== Transactions and options == | |||
[CONFIRM: transaction names and option list against Volume 1 and Volume 2 of the current revision. The text below is a placeholder structure.] | |||
* ITI-71: Get Access Token (the token request). | |||
* Options: [CONFIRM: for example the JWT Token Option and the Client Credentials grant type, against the TI text.] | |||
== Relationship to other profiles == | |||
* [[XUA]]: the SAML-based counterpart for user assertions. | |||
* [[ATNA]]: security audit and mutual authentication (TLS) for the same transactions. | |||
* [[MHD]], [[PMIR]], [[mCSD]], [[SVCM]]: profiles that use IUA for authorization in the MHDS FHIR exchange blueprint. | |||
== Use in FHIR-based architectures == | |||
IUA is categorized under FHIR because it is used with FHIR-based profiles such as MHD. [CONFIRM: wording, and whether to link the MHDS and CH EPR implementations listed in the wider profile documentation.] | |||
== Connectathon testing == | |||
IUA has been tested at IHE Connectathons, most recently in Europe (2024, 2025 and 2026) and Japan (2024). Between 2022 and 2026, 18 vendors tested IUA actors: Authorization Client, Authorization Server and Resource Server. [CONFIRM: figures against the CAT results before posting.] | |||
== Recent changes == | |||
* Revision 2.5 (2026-06-18): Trial Implementation. [CONFIRM: list of changes in this revision.] | |||
* CP-ITI-1331: removes the client_id/client_secret requirement for the Client Credentials grant; passed ballot 67; not yet in the published text. [CONFIRM: publication status.] | |||
* CP-ITI-1324: clarifies that JWT signing is required or optional; passed ballot 66. [CONFIRM: publication status.] | |||
== Open issues == | |||
[CONFIRM: list any open issues from the TI text. None have been confirmed as open as of this draft.] | |||
== Formal Specification == | |||
* [https://profiles.ihe.net/ITI/TF/Volume1/ch-34.html IUA (HTML specification)] | |||
* [https://profiles.ihe.net/ITI/index.html IT Infrastructure Technical Framework] | |||
== Further reading == | |||
* [https://profiles.ihe.net/ITI/HIE-Whitepaper/index.html HIE white paper] | |||
* [CONFIRM: any IUA-specific slides, webinars or videos before adding. No IUA video was found in the search.] | |||
== See Also == | |||
* [[XUA]] | |||
* [[MHD]] | |||
* [[ATNA]] | |||
----- END WIKI MARKUP ----- | |||
Notes for the editor (remove before posting): | |||
* The current page is protected and has an unfilled placeholder in the related-profile text ("< supports IUA in some fashion >" and "< supported as a token type in IUA >"). Those placeholders are on other profile pages. Check before editing. | |||
* The current page links to an old revision. Use the current permanent link when editing. | |||
* The [[...]] links must match existing wiki page names. Check XUA, ATNA, MHD, PMIR, mCSD, SVCM before posting. | |||
Revision as of 10:32, 19 November 2026
PROPOSED UPDATE to https://wiki.ihe.net/index.php/Internet_User_Authorization Wiki markup. Not yet posted. Items in [CONFIRM] need checking before posting.
BEGIN WIKI MARKUP -----
Internet User Authorization (IUA)
Internet User Authorization (IUA) is an IHE IT Infrastructure profile that conveys the identity, attributes and authorizations of a user to a RESTful service. It supports the authorization of transactions made over IHE's HTTP RESTful transports. IUA is the RESTful counterpart of XUA (Cross-Enterprise User Assertion), which uses SAML assertions.
| Status | Trial Implementation, Revision 2.5 (dated 2026-06-18) |
|---|---|
| Domain | IT Infrastructure (ITI) |
| Technology | OAuth 2.0 / 2.1 with JSON Web Tokens (JWT); HTTP RESTful transactions |
| Specification | IUA Volume 1, Chapter 34 |
Overview
IUA defines how a client application obtains an access token from an authorization server and presents it to a resource server. The resource server can then check the user's identity and authorizations before it processes a request.
Actors
- Authorization Client: requests an access token for a user or client application.
- Authorization Server: issues access tokens after authenticating the client.
- Resource Server: accepts access tokens and enforces authorization on requests.
Transactions and options
[CONFIRM: transaction names and option list against Volume 1 and Volume 2 of the current revision. The text below is a placeholder structure.]
- ITI-71: Get Access Token (the token request).
- Options: [CONFIRM: for example the JWT Token Option and the Client Credentials grant type, against the TI text.]
Relationship to other profiles
- XUA: the SAML-based counterpart for user assertions.
- ATNA: security audit and mutual authentication (TLS) for the same transactions.
- MHD, PMIR, mCSD, SVCM: profiles that use IUA for authorization in the MHDS FHIR exchange blueprint.
Use in FHIR-based architectures
IUA is categorized under FHIR because it is used with FHIR-based profiles such as MHD. [CONFIRM: wording, and whether to link the MHDS and CH EPR implementations listed in the wider profile documentation.]
Connectathon testing
IUA has been tested at IHE Connectathons, most recently in Europe (2024, 2025 and 2026) and Japan (2024). Between 2022 and 2026, 18 vendors tested IUA actors: Authorization Client, Authorization Server and Resource Server. [CONFIRM: figures against the CAT results before posting.]
Recent changes
- Revision 2.5 (2026-06-18): Trial Implementation. [CONFIRM: list of changes in this revision.]
- CP-ITI-1331: removes the client_id/client_secret requirement for the Client Credentials grant; passed ballot 67; not yet in the published text. [CONFIRM: publication status.]
- CP-ITI-1324: clarifies that JWT signing is required or optional; passed ballot 66. [CONFIRM: publication status.]
Open issues
[CONFIRM: list any open issues from the TI text. None have been confirmed as open as of this draft.]
Formal Specification
Further reading
- HIE white paper
- [CONFIRM: any IUA-specific slides, webinars or videos before adding. No IUA video was found in the search.]
See Also
END WIKI MARKUP -----
Notes for the editor (remove before posting):
- The current page is protected and has an unfilled placeholder in the related-profile text ("< supports IUA in some fashion >" and "< supported as a token type in IUA >"). Those placeholders are on other profile pages. Check before editing.
- The current page links to an old revision. Use the current permanent link when editing.
- The ... links must match existing wiki page names. Check XUA, ATNA, MHD, PMIR, mCSD, SVCM before posting.