🔐Identity API

Identity Api

One of the basic concept of Microservices we have broken down idenity to be a speprate service which can be indivisually scaled as required and deployed to k8s.

Identity Api uses Identity Server4 to maintain login and generate token.

Key Notes

• The service follows the Open Api Spec and REST standards.

• The service is configured to run using kestrel server on port 1000

• The service exposes a health check at /health and /healthz endpoint.

• The service exposes a swagger endpoint for /swagger only in Development env.

• The service exposes a metric endpoint /metricstext for text based and /metrics for protobuf in prometheus format.

• The service exposes the .well-known endpoint using Identity Server4

• The service uses dapr components

• The service uses sql for Identity based date

Identity Service (Identity Server 4)

This service is built using Identity server 4 and have uses SQLite for the Database and is built using a code first approach.

WellKnown Endpoint Exposed by identity server : https://localhost:5443/.well-known/openid-configuration

{
  "issuer": "https://localhost:5443",
  "jwks_uri": "https://localhost:5443/.well-known/openid-configuration/jwks",
  "authorization_endpoint": "https://localhost:5443/connect/authorize",
  "token_endpoint": "https://localhost:5443/connect/token",
  "userinfo_endpoint": "https://localhost:5443/connect/userinfo",
  "end_session_endpoint": "https://localhost:5443/connect/endsession",
  "check_session_iframe": "https://localhost:5443/connect/checksession",
  "revocation_endpoint": "https://localhost:5443/connect/revocation",
  "introspection_endpoint": "https://localhost:5443/connect/introspect",
  "device_authorization_endpoint": "https://localhost:5443/connect/deviceauthorization",
  "frontchannel_logout_supported": true,
  "frontchannel_logout_session_supported": true,
  "backchannel_logout_supported": true,
  "backchannel_logout_session_supported": true,
  "scopes_supported": [
    "profile",
    "openid",
    "role",
    "tripfeed.write",
    "tripfeed.read",
    "offline_access"
  ],
  "claims_supported": [
    "gender",
    "website",
    "picture",
    "profile",
    "preferred_username",
    "nickname",
    "middle_name",
    "given_name",
    "family_name",
    "name",
    "birthdate",
    "zoneinfo",
    "locale",
    "updated_at",
    "sub",
    "role"
  ],
  "grant_types_supported": [
    "authorization_code",
    "client_credentials",
    "refresh_token",
    "implicit",
    "password",
    "urn:ietf:params:oauth:grant-type:device_code"
  ],
  "response_types_supported": [
    "code",
    "token",
    "id_token",
    "id_token token",
    "code id_token",
    "code token",
    "code id_token token"
  ],
  "response_modes_supported": [
    "form_post",
    "query",
    "fragment"
  ],
  "token_endpoint_auth_methods_supported": [
    "client_secret_basic",
    "client_secret_post"
  ],
  "id_token_signing_alg_values_supported": [
    "RS256"
  ],
  "subject_types_supported": [
    "public"
  ],
  "code_challenge_methods_supported": [
    "plain",
    "S256"
  ],
  "request_parameter_supported": true
}

Getting Started

Identity Service

Create Migrations

• Add Migrations

dotnet ef migrations add InitialCreate -c PersistedGrantDbContext
dotnet ef migrations add InitialCreate -c ConfigurationDbContext
dotnet ef migrations add InitialCreate -c ApplicationDbContext

• Update Database

dotnet ef database update -c  PersistedGrantDbContext
dotnet ef database update -c  ConfigurationDbContext
dotnet ef database update -c  ApplicationDbContext

dotnet run /seed

.NET Commands

Making changes in database Models

dotnet ef migrations add InitialCreate
dotnet ef database update InitialCreate

Run SQL Server local

docker pull mcr.microsoft.com/mssql/server
docker run -e "ACCEPT_EULA=Y" -e "SA_PASSWORD=password@1" -p 1433:1433 --name sql -d mcr.microsoft.com/mssql/server:2017-latest

Run using dapr

dapr run --app-port 1000 --app-id processor --app-protocol http --dapr-http-port 1501 --components-path ../../dapr/components -- dotnet run

Kubernetes

Run in K8s

#spin up the infra
kubectl apply -k Evolution.infra/deploy/k8s/infra/overlays/dev -n evolution

#deploy the service
kubectl apply -k Evolution.Identity/deploy/k8s/identity/overlays/dev -n evolution

#check port-forward 
kubectl port-forward svc/identity-api-cluster-ip 80 -n evolution

Deleteing the resources

#delete the service
kubectl delete -k Evolution.Identity/deploy/k8s/identity/overlays/dev -n evolution

#delete the infra
kubectl delete -k Evolution.infra/deploy/k8s/infra/overlays/dev -n evolution