(Arc4u 6.1.18.x+) Consider rewriting BlazorMsalTokenProvider not to use internal Microsoft interfaces

[vvdb-architecture]

Currently, BlazorMsalTokenProvider uses an internal interface called IAccessTokenProviderAccessor . This interface is accessible but internal to Microsoft's implementation and therefore subject to change. See the source:

namespace Microsoft.AspNetCore.Components.WebAssembly.Authentication.Internal
{
    /// <summary>
    /// This is an internal API that supports the Microsoft.AspNetCore.Components.WebAssembly.Authentication
    /// infrastructure and not subject to the same compatibility standards as public APIs.
    /// It may be changed or removed without notice in any release.
    /// </summary>
    public interface IAccessTokenProviderAccessor
    {
        /// <summary>
        /// This is an internal API that supports the Microsoft.AspNetCore.Components.WebAssembly.Authentication
        /// infrastructure and not subject to the same compatibility standards as public APIs.
        /// It may be changed or removed without notice in any release.
        /// </summary>
        IAccessTokenProvider TokenProvider { get; }
    }
}

There is an equivalent public interface called IAccessTokenProvider. This does exactly the same thing and is public.

In BlazorMsalTokenProvider it's a drop-in replacement and you need to change the namespace to:

using Microsoft.AspNetCore.Components.WebAssembly.Authentication;