Blazor-Auth0-ClientSide 0.6.0-beta-1

Blazor Auth0 Library (client-side)

This is a library for Blazor authentication with OIDC Authorization Code-Grant and Implicit-Grant flows, using Auth0's Universal Login and Silent Login for Blazor v3.0.0-preview5+ client side solutions, the idea behind this is to have an easy way of using Auth0's services in Blazor without the need of the auth0.js library.

Start using it in 3 simple steps!

1. Start by adding a reference to Blazor-Auth0-ClientSide.0.6.0-beta-1 to your Blazor Client Side project

Install-Package Blazor-Auth0-ClientSide -Version 0.6.0-beta-1

2. In Startup.cs, register the service inside ConfigureServices method

public void ConfigureServices(IServiceCollection services)
{

    //...
	
    services.AddScoped<HttpClient>();

    services.AddScoped((sp) =>
    {
	return new Blazor.Auth0.Shared.Models.ClientSettings()
	{
		Auth0Domain = "[Auth0_Domain]",
		Auth0ClientId = "[Auth0_Client_Id]",
		//// Redirection to home can be forced uncommenting the following line this setting primes over Auth0RedirectUri
		// RedirectAlwaysToHome = true,
		//// Uncomment following line to force the user to be authenticated
		// LoginRequired = true
	};
    });
	
    services.AddScoped<Blazor.Auth0.ClientSide.Authentication.AuthenticationService>();
	
    //...

}

Other options include:

• AuthenticationGrant: Allows you to choose between authorization_code (recommended) and implicit_grant authentication flows.

• RedirectAlwaysToHome: When set to true, forces the redirect_uri param to be the home path, this value overrides Auth0RedirectUri

• LoginRequired: When set to true, forces a redirection to the login page in case the user is not authenticated.

• GetUserInfoFromIdToken: When set to true, the serivce will use the id_token payload to build the user info, this is good in case all the user info you require is present in the id_token payload and you want avoid doing an extra call to Auth0, in case that tere's no id_token present in the authentication response the service will fall back gracefully to try to get the user info from an API call to auth0, default value is false

3. Replace the content of App.razor with the following code

@using Blazor.Auth0.Shared.Models.Enumerations
@using Blazor.Auth0.ClientSide.Components
@using Blazor.Auth0.ClientSide.Authentication

@inject AuthenticationService _authService


<AuthComponent ProtectedPaths="protectedPaths">

	@*Will render while determining user's session state*@
	<UndefinedSessionStateContent>
		Determining session state, please wait...
	</UndefinedSessionStateContent>

	@*Will render after determining session state*@
	<AuthorizedContent>

		<Router AppAssembly="typeof(Startup).Assembly">

			<NotFoundContent>
				<p>Sorry, there's nothing at this address.</p>
			</NotFoundContent>

		</Router>

	</AuthorizedContent>

	<UnAuthorizedContent>
		ERROR 401: Unauthorized
	</UnAuthorizedContent>

</AuthComponent>


@code {

    List<string> protectedPaths = new List<string> {
        "fetchdata"
    };

}

Other options include:

• ProtectedPaths: Allows you to indicate a list of paths that requires an authenticated user, only affects if LoginRequired is set to false.

• LoginRequiredOnProtectedPaths: Alters the ProtectedPaths behavior. When set to true redirect the user to the login page automatically, otherwise, the content from the UnAuthorizedContent fragment will be rendered.