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

134 lines
6.0 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.Collections.Generic;
namespace Opc.Ua.Identity
{
/// <summary>
/// Optional probe interface that exposes authentication claims (groups,
/// roles, raw key/value pairs) carried by an authenticated
/// <see cref="IUserIdentity"/>.
/// </summary>
/// <remarks>
/// <para>
/// Designed to be implemented alongside <see cref="IUserIdentity"/>
/// (NOT inherited) so that existing identity types remain on the
/// stable, non-claims contract. Consumers probe via
/// <c>identity as IIdentityClaims</c>.
/// </para>
/// <para>
/// Implementations populate this from the underlying token: a JWT
/// <c>IssuedIdentityToken</c> exposes the decoded JWT claim set; an
/// <c>X509IdentityToken</c> typically projects subject + SAN + EKU; a
/// <c>UserNameIdentityToken</c> projects <c>preferred_username</c>.
/// </para>
/// <para>
/// This interface intentionally has no setters. Claims are populated
/// once by the validating <see cref="IUserTokenAuthenticator"/> and
/// are immutable for the lifetime of the identity.
/// </para>
/// <para>
/// Used by <c>IRoleManager.ResolveGrantedRoles</c> to evaluate the
/// Part 18 §4.4.4 <c>GroupId</c> and <c>Role</c> identity criteria
/// against externally asserted group/role claims (e.g. from an
/// OIDC <c>groups</c> / <c>roles</c> claim, an Entra <c>groups</c>
/// claim, or a Kerberos PAC).
/// </para>
/// </remarks>
public interface IIdentityClaims
{
/// <summary>
/// The raw claim set keyed by claim name. Claim names follow
/// OIDC / Entra conventions where possible — for example
/// <c>sub</c>, <c>iss</c>, <c>aud</c>, <c>exp</c>,
/// <c>preferred_username</c>, <c>email</c>, <c>oid</c>,
/// <c>tid</c>, <c>upn</c>, <c>groups</c>, <c>roles</c>,
/// <c>scope</c>.
/// </summary>
/// <remarks>
/// Values are typically <see cref="string"/>, <see cref="long"/>,
/// <see cref="bool"/>, or <see cref="IReadOnlyList{T}"/> of those.
/// JSON arrays from a JWT body are projected as
/// <see cref="IReadOnlyList{T}"/> of <see cref="string"/>;
/// nested JSON objects are not exposed in this interface and
/// should be flattened by the authenticator using dot notation
/// when needed.
/// </remarks>
IReadOnlyDictionary<string, object?> Claims { get; }
/// <summary>
/// Group identifiers asserted by the identity provider, typically
/// the values of the OIDC / Entra <c>groups</c> claim. Used to
/// evaluate Part 18 §4.4.4 <see cref="IdentityCriteriaType.GroupId"/>.
/// </summary>
/// <remarks>
/// May be empty when the identity provider did not assert group
/// membership. Implementations that source groups from multiple
/// claims (e.g. Entra <c>groups</c> plus a custom
/// <c>group_ids</c> claim) merge them into this list.
/// </remarks>
IReadOnlyList<string> Groups { get; }
/// <summary>
/// Role identifiers asserted by the identity provider, typically
/// the values of the OIDC / Entra <c>roles</c> claim. Used to
/// evaluate Part 18 §4.4.4 <see cref="IdentityCriteriaType.Role"/>.
/// </summary>
/// <remarks>
/// Per Part 18 §4.4.4 a <see cref="IdentityCriteriaType.Role"/>
/// criteria value may be prefixed with the issuer URI separated
/// by a forward slash (<c>iss/roleName</c>). The
/// <c>IRoleManager</c> consumer of this list is responsible for
/// resolving that prefix against
/// <see cref="Claims"/>[<c>iss</c>].
/// </remarks>
IReadOnlyList<string> Roles { get; }
/// <summary>
/// Issuer URI as asserted by the identity provider, mirroring the
/// JWT <c>iss</c> claim. Provided as a convenience for Part 18
/// role-claim prefix resolution and audit logging. May be
/// <see langword="null"/> when the underlying token type does
/// not carry an issuer (e.g. an X509 certificate identity).
/// </summary>
string? Issuer { get; }
/// <summary>
/// The subject identifier asserted by the identity provider,
/// mirroring the JWT <c>sub</c> claim. For X509 identities this
/// is the canonical subject DN; for UserName identities this is
/// the user name. Used as a stable identity key for audit
/// logging.
/// </summary>
string? Subject { get; }
}
}