Files
Marc Schier 0000513cde Pluggable user-identity provider model (#3807)
# Description

Introduces a pluggable user-identity provider model covering all OPC UA
Part 6 §6.5 mechanisms (Anonymous, UserName, X509, IssuedToken/JWT) on
both client and server, with full
`Microsoft.Extensions.DependencyInjection` integration, plus the Part 12
§9 `AuthorizationService` two-phase token-request flow **including
refresh-token rotation**, the Part 12 §8 KeyCredential Push model, and a
clean provider model for OPC 10000-12 §7.2 `ApplicationSelfAdmin`. The
work is split across phase-by-phase commits so it can be reviewed
independently; nothing here changes wire-level behaviour or forces
existing applications to migrate.

### Documentation

All under `Docs/`:

- `IdentityProviders.md` — full developer guide: three-layer model,
recipes, configuration reference, "what gets auto-wired" matrix, JWS
algorithm table, identity-augmenters section, **"Implementing your own
provider"** how-to subsections for Entra / OIDC / Windows / AspNetCore
(sibling files merged in per review feedback).
- `DependencyInjection.md` — `Identity` sections with `appsettings.json`
examples, identity-extension matrix, `WithAuthorizationService` +
`WithKeyCredentialPush` + `AddIdentityAugmenter` extensions documented.
- `RoleBasedUserManagement.md` — claim-criteria callout describing
`IIdentityClaims` probe surface.
- `AuthorizationService.md` — Architecture diagram +
`IAccessTokenProvider` conceptual narrative restored from master; modern
`StartRequestToken` / `FinishRequestToken` flow leads; refresh-token
recipe added.
- `KeyCredentialService.md` — Push model + Pull vs Push vs Bridge
decision matrix + Hybrid (Push + Pull) section; explicit experimental
warning for the bridge.
- `GDS.md` — KeyCredential Push, `StartRequestToken`,
`GdsApplicationSelfAdminProvider`, **shipped Refresh-token support with
rotation policy and audit semantics** all documented.
- `MigrationGuide.md` — User Identity Providers section listing
`[Obsolete]` markers + mechanical recipes; SelfAdmin migration via
`IIdentityAugmenter`; `EnableRefreshTokens` default note.
- `README.md` index entries.

## Checklist

- [x] I have signed the
[CLA](https://opcfoundation.org/license/cla/ContributorLicenseAgreementv1.0.pdf)
and read the
[CONTRIBUTING](https://github.com/OPCFoundation/UA-.NETStandard/blob/master/CONTRIBUTING.md)
doc.
- [x] I have added tests that prove my fix is effective or that my
feature works and increased code coverage.
- [x] I have added all necessary documentation.
- [x] I have verified that my changes do not introduce (new) build or
analyzer warnings.
- [x] I ran **all** tests locally using the **UA.slnx** solution against
at least .net **framework** and .net **10**, and all passed.
- [x] I fixed **all** failing and flaky tests in the CI pipelines and
**all** CodeQL warnings.
- [x] I have addressed **all** PR feedback received.
2026-06-02 01:14:54 +02:00

115 lines
4.6 KiB
C#

/* ========================================================================
* Copyright (c) 2005-2026 The OPC Foundation, Inc. All rights reserved.
*
* OPC Foundation MIT License 1.00
*
* Permission is hereby granted, free of charge, to any person
* obtaining a copy of this software and associated documentation
* files (the "Software"), to deal in the Software without
* restriction, including without limitation the rights to use,
* copy, modify, merge, publish, distribute, sublicense, and/or sell
* copies of the Software, and to permit persons to whom the
* Software is furnished to do so, subject to the following
* conditions:
*
* The above copyright notice and this permission notice shall be
* included in all copies or substantial portions of the Software.
*
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
* EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
* OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
* NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
* HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
* WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
* FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
* OTHER DEALINGS IN THE SOFTWARE.
*
* The complete license agreement can be found here:
* http://opcfoundation.org/License/MIT/1.00/
* ======================================================================*/
using System;
using System.Collections.Generic;
using System.Threading;
using System.Threading.Tasks;
namespace Opc.Ua.Identity
{
/// <summary>
/// A request to issue an access token, used by a server-side
/// Authorization Service (Part 12 §9) implementation. Carries the
/// authenticated principal plus the desired audience / scopes.
/// </summary>
/// <param name="Subject">
/// Stable identifier for the authenticated principal (JWT
/// <c>sub</c> claim).
/// </param>
/// <param name="AudienceUri">
/// The resource URI the issued token is bound to (JWT <c>aud</c>
/// claim). Typically the target server's <c>ApplicationUri</c>.
/// </param>
/// <param name="RequestedScopes">
/// OAuth2 scopes the caller is requesting. The issuer may grant a
/// subset.
/// </param>
/// <param name="AdditionalClaims">
/// Extra claims the issuer should embed into the token (for example
/// <c>groups</c> or <c>roles</c> propagated from a chained identity
/// provider per Part 12 §9.5 "Chained Authorization").
/// </param>
/// <param name="RequestedLifetime">
/// Desired token lifetime. The issuer may shorten this.
/// </param>
public readonly record struct TokenIssuanceRequest(
string Subject,
string AudienceUri,
IReadOnlyList<string> RequestedScopes,
IReadOnlyDictionary<string, object?> AdditionalClaims,
TimeSpan RequestedLifetime);
/// <summary>
/// Issues access tokens on behalf of an Authorization Service
/// (Part 12 §9). Plug-in extension point for the GDS implementation:
/// the default in-box implementation signs JWTs with an ECDSA key
/// resident in the GDS, but a deployment can substitute a corporate
/// CA or a cloud KMS by implementing this interface.
/// </summary>
/// <remarks>
/// <para>
/// The interface is async because real-world issuers (HSMs, cloud
/// KMSs, remote signing services) cannot be assumed to be
/// in-process. The default ECDSA-with-resident-key implementation
/// completes synchronously.
/// </para>
/// <para>
/// Used in P6 to back the modern Part 12 v1.05
/// <c>StartRequestToken</c> / <c>FinishRequestToken</c> server-side
/// flow. The deprecated <c>RequestAccessToken</c> method remains
/// available but uses the same <see cref="ITokenIssuer"/> under the
/// hood.
/// </para>
/// </remarks>
public interface ITokenIssuer
{
/// <summary>
/// Issuer URI placed in the token's <c>iss</c> claim.
/// </summary>
string IssuerUri { get; }
/// <summary>
/// OPC UA issued-token profile URI describing the token format
/// produced by this issuer (e.g.
/// <see cref="Profiles.JwtUserToken"/>).
/// </summary>
string ProfileUri { get; }
/// <summary>
/// Issues an access token. The returned <see cref="AccessToken"/>
/// is owned by the caller and must be disposed.
/// </summary>
ValueTask<AccessToken> IssueAsync(
TokenIssuanceRequest request,
CancellationToken ct = default);
}
}