Skip to content

Latest commit

 

History

History
99 lines (65 loc) · 3.67 KB

Configure-Ubuntu-PostgreSQL-Tutorial.md

File metadata and controls

99 lines (65 loc) · 3.67 KB

Introduction

Tutorial covers configuration of Admin on Ubuntu 18.04 with fresh instance of PostgreSQL database.

Prerequisites

.NET Core 2.2 SDK

Instructions from: https://dotnet.microsoft.com/download/linux-package-manager/ubuntu18-04/sdk-2.2.101

wget -q https://packages.microsoft.com/config/ubuntu/18.04/packages-microsoft-prod.deb
sudo dpkg -i packages-microsoft-prod.deb

sudo add-apt-repository universe
sudo apt-get install apt-transport-https
sudo apt-get update
sudo apt-get install dotnet-sdk-2.2

PostgreSQL

Instructions from: https://linuxize.com/post/how-to-install-postgresql-on-ubuntu-18-04/

sudo apt update
sudo apt install postgresql postgresql-contrib

Throughout tutorial we will use PostgreSQL running on localhost and default port 5432 with username/password combination postgres/postgres. You can update connection strings with your own or if you want to follow everything exactly then after installing PostgreSQL you will need to change password of postgres user:

sudo -u postgres psql
ALTER USER postgre WITH PASSWORD 'postgres';

IDE

Console commands will be used throghout the tutorial but for code editing it is recommended to use dedicated IDE. I've got good experience with Visual Studio Code and Rider.

Cloning Admin

git clone https://github.com/skoruba/IdentityServer4.Admin

Adjustments for PostgreSQL

By default everything is configured for Microsoft SQL Server, but fortunately it's pretty easy to change.

Replace connection strings

First change connection strings in src/Skoruba.IdentityServer4.Admin/appsettings.json and src/Skoruba.IdentityServer4.STS.Identity/appsettings.json and replace them with following connection string:

Server=localhost; User Id=postgres; Database=is4admin; Port=5432; Password=postgres; SSL Mode=Prefer; Trust Server Certificate=true

Install required packages

Next we need to install PostgreSQL support for EntityFramework Core in Skoruba.IdentityServer4.Admin and Skoruba.IdentityServer4.STS.Identity in order to do that run in each project's directory:

dotnet add src/Skoruba.IdentityServer4.Admin package Npgsql.EntityFrameworkCore.PostgreSQL
dotnet add src/Skoruba.IdentityServer4.Admin package Npgsql.EntityFrameworkCore.PostgreSQL.Design
dotnet add src/Skoruba.IdentityServer4.STS.Identity package Npgsql.EntityFrameworkCore.PostgreSQL
dotnet add src/Skoruba.IdentityServer4.STS.Identity package Npgsql.EntityFrameworkCore.PostgreSQL.Design

Replace UseSqlServer with UseNpgsql

In src/Skoruba.IdentityServer4.Admin and src/Skoruba.IdentityServer4.STS.Identity in Helpers/StartupHelpers.cs replace all occurences of UseSqlServer with UseNpgsql. This will inform EntityFramework that PostgreSQL will be used instead of SQL Server.

Final setup

Generate initial migrations

dotnet ef migrations add DbInit -c AdminDbContext -o Data/Migrations
dotnet ef database update -c AdminDbContext

Run STS and Admin

First run STS in src/Skoruba.IdentityServer4.STS.Identity launch:

dotnet run

Admin also needs to seed the database so seperate terminal in src/Skoruba.IdentityServer4.Admin we add additional seed parameter:

dotnet run /seed

After that we should have STS listening on http://localhost:5000 and Admin on http://localhost:9000. We can go to the latter and we should be redirected to our STS for authentication (admin/Pa$$word123 is the default combination).

Final thoughts

There are many more steps required before IS4 and Admin panel are sufficiently hardened to be used in production scenario. Please bear in mind that this tutorial serves only as a quickstart.