Skip to content

Latest commit

 

History

History
103 lines (70 loc) · 5.06 KB

README.md

File metadata and controls

103 lines (70 loc) · 5.06 KB
Raw

User Authentication Sample with API access

This code example allows you to do two things:

  • You can log on as a user by using the Authorization Code Flow
  • You can also connect to the sample API by using an access token

Prerequisites

If you want to use HelseID not only to log on as a user, but also to connect to an API, you'll need to run the Sample API:

  • Go to the SampleAPI folder and run the command dotnet run.

Architecture

The client application is based on ASP.NET Core. You can find relevant code in:

  • The Startup class: this is the initial configuration of the project
  • The OpenIdConnectOptionsInitializer class sets up the OpenID Connect user login, using IClientAssertionsBuilder from the Common project
  • The IUserSessionDataStore interface abstracts the persisting of user tokens
  • The AccessTokenUpdater class updates access tokens when they have expired

HelseID is an Authorization Server that is based upon the protocols OAuth2 and OpenId Connect. Before we can use HelseID, we need to have a client registered and configured in the HelseID Server Configuration. This sample code uses pre-existing clients which are already present in the development environment for HelseID. The configuration for these clients are configured in the Configuration project located elsewhere in this repo.

User login

When you start the sample with dotnet run on the command line, you'll need to connect a web browser to the address that shows up in the console:

Now listening on: https://localhost:5151
Application started. Press Ctrl+C to shut down.

the default address is https://localhost:5151, but you can change the port number in the file ConfigurationValues.cs in the Configuration folder in the hierarchy above this folder. If you want to change the port number, change the ApiAccessWebServerPortconstant in that file.

Click "Login" and use the "Test IDP". Then log in as a well-known test person. You should be redirected back to the application at https://localhost:5151.

API Access

Next, we can get access to the Sample API by running the API Access application provided here.

This is done by using the access token that we got from the authentication process as a bearer token when accessing the Sample API.

The access token is set as a Bearer token in the Authorization Header, after which we call the API and retrieve the result.

Requirements

The .NET 8 SDK is required to build the program.

If you need to use this sample to access an API, you will need to start the Sample API project in a separate terminal. Then, you can run this application.

Standard mode (user logon with API access)

To run the sample in standard mode (user logon with API access), enter the following on the command line inside this folder:

dotnet run

User login only

To run the sample as a user login only application, start the application with the extra option:

dotnet run --user-login-only

Use of request objects (for use of a child organization number)

If you want to send a child organization number (underenhet) as part of the claim to the API, you will need to set this organization number as part of a request object that is sent to HelseID. If this organization number is attached to the client in HelseID, you will receive a claim of type helseid://claims/client/claims/orgnr_child as part of the access token. To do this, you can start the application with the extra option:

dotnet run --use-request-objects

Use of resource indicators

If you need to access more than one API, the preferred solution is to use resource indicators as part of the call to HelseID. To use the resource indicators sample, you will need to start the application with an extra option:

dotnet run --use-resource-indicators

You will also need to start two instances of the Sample API project. See the readme file in that folder for more information on how to do this.

Use of token exchange

If you want to use the token exchange sample, you will need to start the application with an extra option:

dotnet run --use-token-exchange

In addition to start the Sample API project, you will also need to start the Sample API for token exchange project. Look into that project folder for more information.

Use of multi-tenancy

Multi-tenancy is a pattern that allows multiple consumers of a software vendor to use the same instance of the vendor’s software. The consequence of this is that a multi-tenant system can set the parent organization number for a token request. In order to do this, use the extra option

dotnet run --use-multi-tenant

To list all options:

dotnet run -- --help