{"id":26667,"date":"2020-05-20T00:00:00","date_gmt":"2020-05-19T22:00:00","guid":{"rendered":"https:\/\/blexin.com\/?p=26667"},"modified":"2021-06-09T12:13:26","modified_gmt":"2021-06-09T10:13:26","slug":"angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker","status":"publish","type":"post","link":"https:\/\/blexin.com\/it\/blog\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\/","title":{"rendered":"Angular, Microservizi e Autenticazione con IdentityServer, MongoDB e Docker"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

In un mio\u00a0articolo precedente\u00a0<\/a>, abbiamo parlato di microservizi e come autenticare un client Angular con essi usando IdentityServer come authentication authority. In quel caso, ho usato la configurazione in memoria per semplificare il concetto, ma in un’applicazione reale abbiamo bisogno di salvare i dati in uno storage persistente come un database.<\/p>\n\n\n\n

Visto che in un progetto ho usato MongoDB per alcuni microservizi, ho pensato fosse utile usare l\u2019istanza di Mongo per salvare anche i dati di IdentityServer, ovviamente in un database separato, e la cosa ha avuto dei risvolti interessanti che vale la pena raccontare. Inoltre, in uno scenario di sviluppo reale, non avrete mai tutti i microservizi e i client in uno stesso repository, quindi, lavorare in localhost pu\u00f2 diventare un problema, che per\u00f2 \u00e8 facilmente risolvibile utilizzando docker e docker-compose. Anche questo aspetto ha dei risvolti interessanti perch\u00e9 vi mette di fronte ad alcune considerazioni di networking che in localhost sfuggono sicuramente.<\/p>\n\n\n\n

IdentityServer e MongoDB<\/strong><\/h2>\n\n\n\n

Cominciamo dall\u2019integrazione di MongoDB con IdentityServer. Esistono alcune librerie pronte all’uso per questo scopo, ma le migliori utilizzano entity framework, come layer intermedio per archiviare dati su MongoDB. Non capisco il motivo dell’uso di un ORM con un database NoSql, penso che non abbia senso, ma ho accettato l\u2019idea che si tratti di una comodit\u00e0 per poter cambiare storage quando riutilizzo qualcosa in un progetto differente, perch\u00e8 diciamocelo\u2026 cambiare database in un progetto in produzione \u00e8 una favola che viene raccontata ai bambini e ai giovani programmatori.<\/p>\n\n\n\n

Ho quindi utilizzato una mia implementazione generica del Repository<\/em> pattern per MongoDB:<\/p>\n\n\n

\npublic interface IRepository\n{\n\u00a0\u00a0\u00a0\u00a0IQueryable<T> All<T>() where T : class, new();\n\u00a0\u00a0\u00a0\u00a0IQueryable<T> Where<T>(Expression<Func<T, bool>> expression) where T : class, new();\n\u00a0\u00a0\u00a0\u00a0T Single<T>(Expression<Func<T, bool>> expression) where T : class, new();\n\u00a0\u00a0\u00a0\u00a0void Delete<T>(Expression<Func<T, bool>> expression) where T : class, new();\n\u00a0\u00a0\u00a0\u00a0void Add<T>(T item) where T : class, new();\n\u00a0\u00a0\u00a0\u00a0void Add<T>(IEnumerable<T> items) where T : class, new();\n}\n\u00a0\npublic class MongoRepository : IRepository\n{\n\u00a0\u00a0\u00a0\u00a0private readonly IMongoClient _client;\n\u00a0\u00a0\u00a0\u00a0private readonly IMongoDatabase _database;\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0public MongoRepository(string mongoConnection, string mongoDatabaseName)\n\u00a0\u00a0\u00a0\u00a0{\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0_client = new MongoClient(mongoConnection);\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0_database = _client.GetDatabase(mongoDatabaseName);\n\u00a0\u00a0\u00a0\u00a0}\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0public IQueryable<T> All<T>() where T : class, new()\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0=> _database.GetCollection<T>(typeof(T).Name).AsQueryable();\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0public IQueryable<T> Where<T>(System.Linq.Expressions.Expression<Func<T, bool>> expression) where T : class, new()\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0=> All<T>().Where(expression);\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0public void Delete<T>(System.Linq.Expressions.Expression<Func<T, bool> predicate) where T : class, new()\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0=> _database.GetCollection<T>(typeof(T).Name).DeleteMany(predicate);\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0public T Single<T>(System.Linq.Expressions.Expression<Func<T, bool>> expression) where T : class, new()\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0=> All<T>().Where(expression).SingleOrDefault();\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0public void Add<T>(T item) where T : class, new()\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0=> _database.GetCollection<T>(typeof(T).Name).InsertOne(item);\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0public void Add<T>(IEnumerable<T> items) where T : class, new()\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0=> _database.GetCollection<T>(typeof(T).Name).InsertMany(items);\n}\n<\/pre><\/div>\n\n\n
Niente di complicato, \u00e8 un semplice utilizzo del driver C# ufficiale per MongoDB per implementare le operazioni CRUD del repository. Per poter usare il repository con IdentityServer, dobbiamo implementare le interfacce IResourceStore, IPersistedGrantStore<\/strong> e IClientStore<\/strong> con cui IdentityServer recupera le Resource, i Grant e i Client da utilizzare nel processo di autenticazione e generazione del token. A titolo di esempio, vi riporto l\u2019implementazione di IClientStore<\/strong>, le restanti classi le trovate sul mio repository GitHub:<\/p>\n\n\n
\npublic class RepositoryClientStore : IClientStore\n{\n\u00a0\u00a0\u00a0\u00a0protected IRepository _repository;\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0public RepositoryClientStore(IRepository repository)\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0=> _repository = repository;\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0public Task<Client> FindClientByIdAsync(string clientId)\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0=> Task.FromResult(_repository.Single<Client>(c => c.ClientId == clientId));\n}\n<\/pre><\/div>\n\n\n
Creiamo una classe di helpers per registrare tutte queste interfacce in modo da rendere pi\u00f9 fluente la configurazione dei servizi:<\/p>\n\n\n
\npublic static class RepositoryExtensions\n{\n\u00a0\u00a0\u00a0\u00a0public static IIdentityServerBuilder AddMongoRepository(\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0this IIdentityServerBuilder builder,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0string mongoConnection,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0string mongoDatabaseName)\n\u00a0\u00a0\u00a0\u00a0{\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0builder.Services.AddTransient<IRepository, MongoRepository>(\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0s => new MongoRepository(mongoConnection, mongoDatabaseName));\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0return builder;\n\u00a0\u00a0\u00a0\u00a0}\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0public static IIdentityServerBuilder AddClients(this IIdentityServerBuilder builder)\n\u00a0\u00a0\u00a0\u00a0{\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0builder.Services.AddTransient<IClientStore, RepositoryClientStore>();\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0builder.Services.AddTransient<ICorsPolicyService, InMemoryCorsPolicyService>();\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0return builder;\n\u00a0\u00a0\u00a0\u00a0}\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0public static IIdentityServerBuilder AddIdentityApiResources(this IIdentityServerBuilder builder)\n\u00a0\u00a0\u00a0\u00a0{\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0builder.Services.AddTransient<IResourceStore, RepositoryResourceStore>();\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0return builder;\n\u00a0\u00a0\u00a0\u00a0}\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0public static IIdentityServerBuilder AddPersistedGrants(this IIdentityServerBuilder builder)\n\u00a0\u00a0\u00a0\u00a0{\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0builder.Services.AddSingleton<IPersistedGrantStore, RepositoryPersistedGrantStore>();\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0return builder;\n\u00a0\u00a0\u00a0\u00a0}\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \n}\n<\/pre><\/div>\n\n\n
Niente di complicato, \u00e8 un semplice utilizzo del driver C# ufficiale per MongoDB per implementare le operazioni CRUD del repository. Per poter usare il repository con IdentityServer, dobbiamo implementare le interfacce IResourceStore, IPersistedGrantStore<\/strong> e IClientStore<\/strong> con cui IdentityServer recupera le Resource, i Grant e i Client da utilizzare nel processo di autenticazione e generazione del token. A titolo di esempio, vi riporto l\u2019implementazione di IClientStore<\/strong>, le restanti classi le trovate sul mio repository GitHub:<\/p>\n\n\n
\npublic class RepositoryClientStore : IClientStore\n{\n\u00a0\u00a0\u00a0\u00a0protected IRepository _repository;\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0public RepositoryClientStore(IRepository repository)\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0=> _repository = repository;\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0public Task<Client> FindClientByIdAsync(string clientId)\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0=> Task.FromResult(_repository.Single<Client>(c => c.ClientId == clientId));\n}\n<\/pre><\/div>\n\n\n
Creiamo una classe di helpers per registrare tutte queste interfacce in modo da rendere pi\u00f9 fluente la configurazione dei servizi:<\/p>\n\n\n
\npublic static class RepositoryExtensions\n{\n\u00a0\u00a0\u00a0\u00a0public static IIdentityServerBuilder AddMongoRepository(\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0this IIdentityServerBuilder builder,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0string mongoConnection,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0string mongoDatabaseName)\n\u00a0\u00a0\u00a0\u00a0{\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0builder.Services.AddTransient<IRepository, MongoRepository>(\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0s => new MongoRepository(mongoConnection, mongoDatabaseName));\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0return builder;\n\u00a0\u00a0\u00a0\u00a0}\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0public static IIdentityServerBuilder AddClients(this IIdentityServerBuilder builder)\n\u00a0\u00a0\u00a0\u00a0{\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0builder.Services.AddTransient<IClientStore, RepositoryClientStore>();\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0builder.Services.AddTransient<ICorsPolicyService, InMemoryCorsPolicyService>();\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0return builder;\n\u00a0\u00a0\u00a0\u00a0}\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0public static IIdentityServerBuilder AddIdentityApiResources(this IIdentityServerBuilder builder)\n\u00a0\u00a0\u00a0\u00a0{\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0builder.Services.AddTransient<IResourceStore, RepositoryResourceStore>();\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0return builder;\n\u00a0\u00a0\u00a0\u00a0}\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0public static IIdentityServerBuilder AddPersistedGrants(this IIdentityServerBuilder builder)\n\u00a0\u00a0\u00a0\u00a0{\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0builder.Services.AddSingleton<IPersistedGrantStore, RepositoryPersistedGrantStore>();\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0return builder;\n\u00a0\u00a0\u00a0\u00a0}\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \n}\n<\/pre><\/div>\n\n\n
A questo punto la configurazione diventa banale:<\/p>\n\n\n
\npublic void ConfigureServices(IServiceCollection services)\n{\n\u00a0\u00a0\u00a0\u00a0...\n\u00a0\u00a0\u00a0\u00a0var builder = services.AddIdentityServer(options =>\n\u00a0\u00a0\u00a0\u00a0{\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0options.Events.RaiseErrorEvents = true;\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0options.Events.RaiseInformationEvents = true;\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0options.Events.RaiseFailureEvents = true;\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0options.Events.RaiseSuccessEvents = true;\n\u00a0\u00a0\u00a0\u00a0})\n\u00a0\u00a0\u00a0\u00a0.AddMongoRepository(\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Configuration.GetValue<string>("MONGO_CONNECTION"),\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Configuration.GetValue<string>("MONGO_DATABASE_NAME"))\n\u00a0\u00a0\u00a0\u00a0.AddClients()\n\u00a0\u00a0\u00a0\u00a0.AddIdentityApiResources()\n\u00a0\u00a0\u00a0\u00a0.AddPersistedGrants();\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0seedDatabase(services);\n\u00a0\u00a0\u00a0\u00a0...\n}\n<\/pre><\/div>\n\n\n
Ho anche aggiunto un metodo privato seedDatabase()<\/strong>che inserisce nel database i dati che usavamo in memoria se rileva che le rispettive collection sono vuote:<\/p>\n\n\n
\nprivate void seedDatabase(IServiceCollection services)\n{\n\u00a0\u00a0\u00a0\u00a0configureMongoDriverIgnoreExtraElements();\n\u00a0\u00a0\u00a0\u00a0var sp = services.BuildServiceProvider();\n\u00a0\u00a0\u00a0\u00a0var repository = sp.GetService<IRepository>();\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0if (repository.All<Client>().Count() == 0)\n\u00a0\u00a0\u00a0\u00a0{\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0foreach (var client in Config.Clients)\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0{\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0repository.Add<Client>(client);\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0}\n\u00a0\u00a0\u00a0\u00a0}\n\u00a0\u00a0\u00a0\u00a0...\n}\n<\/pre><\/div>\n\n\n
Dato che andiamo a salvare su Mongo degli oggetti non nostri, ma di IdentityServer, dobbiamo istruire MongoDB sul fatto che non trover\u00e0 in queste classi alcuni elementi extra che vengono aggiunti dal motore del database durante la creazione dei documenti, come ad esempio la propriet\u00e0 _id<\/strong>. Per farlo, ho creato un metodo privato che chiamo prima dell\u2019eventuale inserimento dei dati, configureMongoDriverIgnoreExtraElements():<\/strong><\/p>\n\n\n
\nprivate void configureMongoDriverIgnoreExtraElements()\n{\n\u00a0\u00a0\u00a0\u00a0var pack = new ConventionPack();\n\u00a0\u00a0\u00a0\u00a0pack.Add(new IgnoreExtraElementsConvention(true));\n\u00a0\u00a0\u00a0\u00a0ConventionRegistry.Register("IdentityServer Mongo Conventions", pack, t => true);\n}\n<\/pre><\/div>\n\n\n
In teoria abbiamo terminato, andiamo adesso a testare la nostra configurazione.<\/p>\n\n\n\n
Docker e Docker Compose<\/strong><\/h2>\n\n\n\n
Visto che dobbiamo tirare su il demone di MongoDB, approfittiamo per cominciare a configurare il nostro\u00a0docker-compose<\/em>, dove al momento mettiamo solo MongoDB. Se siete a digiuno di Docker potete leggere\u00a0un mio precedente articolo<\/a>\u00a0oppure il mio libro gratuito che parla anche di Kubernetes (https:\/\/www.syncfusion.com\/ebooks\/using-netcore-docker-and-kubernetes-succinctly<\/a>).<\/p>\n\n\n\n
\u0116 possibile creare manualmente il file docker-compose.yml<\/strong> nella root del progetto, oppure utilizzare i tool di Docker per Visual Studio Code:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Modifichiamo lo script per tirare su il container con MongoDB e esponiamo la porta su localhost. In generale, non \u00e8 una bella cosa lasciare che Mongo salvi i dati all\u2019interno del container, ma per i nostri esempi e limitatamente alla fase di sviluppo, possiamo evitare di creare un volume per essi:<\/p>\n\n\n
\nversion: '3.4'\nservices:\n\u00a0mongodb:\n\u00a0\u00a0\u00a0image: mongo:latest\n\u00a0\u00a0\u00a0hostname: mongodb\n\u00a0\u00a0\u00a0ports:\n\u00a0\u00a0\u00a0\u00a0\u00a0- "27017:27017"\n<\/pre><\/div>\n\n\n
A questo punto possiamo eseguire lo script (docker-compose up<\/strong>) e una volta su, possiamo lanciare il progetto IdentityServer<\/em> con il classico dotnet run<\/strong>. Se tutto va a buon fine vedrete le collection del database Mongo:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Creiamo adesso un Dockerfile per poterlo containerizzare il nostro IdentityServer. Nella folder del progetto identityserver<\/strong>, creiamo un file Dockerfile<\/strong> che conterr\u00e0 le seguenti istruzioni:<\/p>\n\n\n
\nFROM mcr.microsoft.com\/dotnet\/core\/sdk:3.1 AS build\nWORKDIR \/app\nCOPY . .\nRUN dotnet restore\nRUN dotnet publish -c Release -o out\n\u00a0\u00a0\nFROM mcr.microsoft.com\/dotnet\/core\/aspnet:3.1 AS runtime\nWORKDIR \/app\nCOPY --from=build \/app\/out .\/\nENTRYPOINT ["dotnet", "identityserver.dll"]\n<\/pre><\/div>\n\n\n
Aggiungiamo anche un .Dockerignore<\/strong> per escludere dalla copia dei file nel container le cartelle bin<\/strong> e obj<\/strong>:<\/p>\n\n\n
\n\/bin\n\/obj\n<\/pre><\/div>\n\n\n
Aggiungiamo la build del Dockerfile al nostro script docker-compose.yml<\/strong> in modo da avere tutto pronto per il client e i microservizi:<\/p>\n\n\n
\nversion: '3.4'\nservices:\n\u00a0identityserver:\n\u00a0\u00a0\u00a0build: .\/identityserver\n\u00a0\u00a0\u00a0environment:\n\u00a0\u00a0\u00a0\u00a0\u00a0- MONGO_CONNECTION=mongodb:\/\/mongodb\n\u00a0\u00a0\u00a0\u00a0\u00a0- MONGO_DATABASE_NAME=identityserber\n\u00a0\u00a0\u00a0ports:\n\u00a0\u00a0\u00a0\u00a0\u00a0- "5000:80"\n\u00a0\u00a0\u00a0depends_on:\n\u00a0\u00a0\u00a0\u00a0\u00a0- mongodb\n\u00a0\u00a0\n\u00a0mongodb:\n\u00a0\u00a0\u00a0image: mongo:latest\n\u00a0\u00a0\u00a0hostname: mongodb\n\u00a0\u00a0\u00a0ports:\n\u00a0\u00a0\u00a0\u00a0\u00a0- "27017:27017"\n<\/pre><\/div>\n\n\n
In realt\u00e0, non c\u2019\u00e8 pi\u00f9 bisogno di esporre la porta di MongoDB su localhost<\/em>, dato che il container identityserver<\/em> si connetter\u00e0 a Mongo utilizzando la network di default creata da Docker e risolver\u00e0 l\u2019indirizzo del database attraverso il nome del service (mongodb<\/em>). Nonostante questo, ho lasciato il forwarding della porta per comodit\u00e0, in modo da potermi sempre collegare con un client come Robo 3T <\/a>, per ispezionare le collection. Lanciando il comando docker-compose up<\/strong>, viene prima creata l\u2019immagine per IdentityServer (solo la prima volta) e poi lanciati entrambi i container, quindi aprendo il browser all\u2019indirizzo http:\/\/localhost:5000\/account\/login<\/a><\/strong> vedremo IdentityServer risponderci correttamente:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
A questo punto, possiamo lanciare il client Angular e vedere se riusciamo ad eseguire l\u2019autenticazione. Andiamo nella cartella client-angular<\/strong> e lanciamo il solito comando ng serve<\/strong>, apriamo il browser all\u2019indirizzo http:\/\/localhost:4200<\/a><\/strong> e verifichiamo di essere reindirizzati alla pagina di autenticazione:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Purtroppo, nonostante la pagina di autenticazione sia raggiungibile, otteniamo un errore CORS<\/em>, che sembrerebbe legittimo a causa della differenza di porta tra client (4200) e server (5000). Ma allora perch\u00e9 nell\u2019articolo precedente lo stesso esempio funzionava senza problemi? Premesso che spesso e volentieri IdentityServer risponde con un errore CORS anche per errori diversi come, ad esempio un errore di accesso ai dati, in questo caso il problema segnalato \u00e8 quello giusto.<\/p>\n\n\n\n
Nell\u2019articolo precedente, le origini dei Client registrati venivano automaticamente aggiunti alle origini autorizzate, quindi il localhost:4200<\/strong> dovrebbe essere tra queste. Se per\u00f2 consultiamo la documentazione ufficiale, alla sezione CORS <\/a>scopriamo un effetto collaterale del non aver usato Entity Framework:<\/p>\n\n\n\n
\u201cThis default CORS implementation will be in use if you are using either the \u201cin-memory\u201d or EF-based client configuration that we provide. If you define your own IClientStore, then you will need to implement your own custom CORS policy service (see below)\u201d.<\/em><\/p>\n\n\n\n
Quindi non ci scoraggiamo e implementiamo il nostro CORS policy service:<\/p>\n\n\n
\npublic class RepositoryCorsPolicyService : ICorsPolicyService\n{\n\u00a0\u00a0\u00a0\u00a0private readonly string[] _allowedOrigins;\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0public RepositoryCorsPolicyService(IRepository repository)\n\u00a0\u00a0\u00a0\u00a0{\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0_allowedOrigins = repository.All<Client>().SelectMany(x => x.AllowedCorsOrigins).ToArray();\n\u00a0\u00a0\u00a0\u00a0}\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0public Task<bool> IsOriginAllowedAsync(string origin)\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0=> Task.FromResult(_allowedOrigins.Contains(origin));\n}\n<\/pre><\/div>\n\n\n
Non ci resta che registrare la nostra implementazione:<\/p>\n\n\n
\npublic void ConfigureServices(IServiceCollection services)\n{\n\u00a0\u00a0\u00a0\u00a0...\n\u00a0\u00a0\u00a0\u00a0var builder = services.AddIdentityServer(options =>\n\u00a0\u00a0\u00a0\u00a0{\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0...\n\u00a0\u00a0\u00a0\u00a0})\n\u00a0\u00a0\n\u00a0\u00a0\u00a0\u00a0...\n\u00a0\u00a0\u00a0\u00a0services.AddSingleton<ICorsPolicyService, RepositoryCorsPolicyService>();\n}\n<\/pre><\/div>\n\n\n
Ricordatevi di aggiungere la vostra registrazione DOPO AddIdentityServer()<\/strong>, altrimenti sar\u00e0 sovrascritta da quella standard che non interrogher\u00e0 i vostri Client. Forziamo la rigenerazione dell\u2019immagine Docker utilizzando il comando docker-compose build –no-cache<\/strong> e riproviamo con docker-compose up<\/strong>:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Questa volta tutto funzioner\u00e0 correttamente, dandoci accesso all\u2019applicazione subito dopo l\u2019autenticazione. Se provate a lanciare anche i microservizi vedrete che risponderanno senza problemi. Finito quindi? Per completare il giro non ci resta che dockerizzare anche i due microservizi, rendendo configurabili i parametri di comunicazione con IdentityServer, dato che non siamo pi\u00f9 in localhost, ma nella rete di default di Docker:<\/p>\n\n\n
\npublic void ConfigureServices(IServiceCollection services)\n{\n\u00a0\u00a0\u00a0\u00a0services.AddAuthentication(options =>\n\u00a0\u00a0\u00a0\u00a0{\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0...\n\u00a0\u00a0\u00a0\u00a0}).AddJwtBearer(o =>\n\u00a0\u00a0\u00a0\u00a0{\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0o.Authority = Configuration.GetValue<string>("IDENTITY_AUTHORITY");\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0o.Audience = Configuration.GetValue<string>("IDENTITY_AUDIENCE");\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0o.RequireHttpsMetadata = Configuration.GetValue<bool>("IDENTITY_REQUIREHTTPSMETADATA");\n\u00a0\u00a0\u00a0\u00a0});\n\u00a0\u00a0\u00a0\u00a0...\n}\n<\/pre><\/div>\n\n\n
A questo punto, possiamo utilizzare lo stesso Dockerfile usato per IdentityServer (sono entrambe applicazioni ASP.NET Core) in cui modifichiamo solo il nome dell\u2019assembly da lanciare su ENTRYPOINT<\/strong>:<\/p>\n\n\n
\n...\nENTRYPOINT ["dotnet", "microservice1.dll"]\n\u00a0\u00a0\n...\nENTRYPOINT ["dotnet", "microservice2.dll"]\n<\/pre><\/div>\n\n\n
Modifichiamo il file docker-compose.yml<\/strong> aggiungendo i due servizi:<\/p>\n\n\n
\nversion: '3.4'\nservices:\n\u00a0microservice1:\n\u00a0\u00a0\u00a0build: .\/microservice1\n\u00a0\u00a0\u00a0environment:\n\u00a0\u00a0\u00a0\u00a0\u00a0- IDENTITY_AUTHORITY=http:\/\/identityserver\n\u00a0\u00a0\u00a0ports:\n\u00a0\u00a0\u00a0\u00a0\u00a0- "5002:80"\n\u00a0\u00a0\u00a0depends_on:\n\u00a0\u00a0\u00a0\u00a0\u00a0- identityserver\n\u00a0\u00a0\n\u00a0microservice2:\n\u00a0\u00a0\u00a0build: .\/microservice2\n\u00a0\u00a0\u00a0environment:\n\u00a0\u00a0\u00a0\u00a0\u00a0- IDENTITY_AUTHORITY=http:\/\/identityserver\n\u00a0\u00a0\u00a0ports:\n\u00a0\u00a0\u00a0\u00a0\u00a0- "5003:80"\n\u00a0\u00a0\u00a0depends_on:\n\u00a0\u00a0\u00a0\u00a0\u00a0- identityserver\n\u00a0\u00a0\n\u00a0identityserver:\n\u00a0\u00a0\u00a0build: .\/identityserver\n\u00a0\u00a0\u00a0...\n\u00a0\u00a0\n\u00a0mongodb:\n\u00a0\u00a0\u00a0image: mongo:latest\n\u00a0\u00a0\u00a0...\n<\/pre><\/div>\n\n\n
Notate che l\u2019indirizzo dell\u2019authority non \u00e8 pi\u00f9 http:\/\/localhost:5000<\/a><\/strong> ma lo impostiamo su http:\/\/identityserver<\/a><\/strong>, utilizzando quindi il nome del servizio per risolvere l\u2019ip del container di identityserver nella rete di default creata da Docker per noi. Lanciamo il comando docker-compose up<\/strong>, che impiegher\u00e0 un po\u2019 di tempo in pi\u00f9 per creare le immagini dei microservizi, e testiamo le invocazioni:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Come potete notare, riceviamo un errore 401 perch\u00e8 il nostro token non risulta valido a causa del valore di issuer<\/em>. La documentazione ufficiale dello standard JWT <\/a>ci dice:<\/p>\n\n\n\n
\u201cThe JWT MUST contain an “iss” (issuer) claim that contains a unique identifier for the entity that issued the JWT. In the absence of an application profile specifying otherwise,compliant applications MUST compare issuer values using the Simple String Comparison method defined in Section 6.2.1 of RFC39862\u201d<\/em><\/p>\n\n\n\n
In localhost tutto funzionava perch\u00e9 IdentityServer genera per noi questo valore, come chiaramente espresso dalla documentazione ufficale<\/a>:<\/p>\n\n\n\n
\u201cIssuerUri: Set the issuer name that will appear in the discovery document and the issued JWT tokens. It is recommended to not set this property, which infers the issuer name from the host name that is used by the clients.\u201d<\/em><\/p>\n\n\n\n
Quindi, alla generazione del token richiesta dal nostro cliente, viene utilizzato come issuer http:\/\/localhost:5000<\/a><\/strong>, mentre il nostro microservizio contatta IdentityServer per la validazione del token utilizzando l\u2019authority http:\/\/identityserver<\/a><\/strong> che abbiamo configurato nello script docker-compose. In produzione non avremmo nessun problema, dato che questi coinciderebbero, ma in questo caso ibrido invece dobbiamo forzare la mano di IdentityServer, utilizzando un IssuerUri<\/strong> fissato:<\/p>\n\n\n
\nvar builder = services.AddIdentityServer(options =>\n{\noptions.IssuerUri = Configuration.GetValue<string>("ISSUER_URI");\n...\n})\n.AddMongoRepository(\nConfiguration.GetValue<string>("MONGO_CONNECTION"),\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Configuration.GetValue<string>("MONGO_DATABASE_NAME"))\n.AddClients()\n.AddIdentityApiResources()\n.AddPersistedGrants();\n<\/pre><\/div>\n\n\n
Conclusioni<\/strong><\/h2>\n\n\n\n
Con questa modifica tutto torna a funzionare correttamente! Potete verificare voi stessi scaricando ed eseguendo i sorgenti che trovate qui: https:\/\/github.com\/apomic80\/angular-microservices-identityserver<\/a>.<\/p>\n\n\n\n
Se volete approfondire Docker e Docker Compose, potete guardare le registrazioni delle dirette del nostro Antonio, che ha trattato tematiche relative a DevOps sul suo canale Twitch:\u00a0https:\/\/www.twitch.tv\/turibbio<\/a>.<\/p>\n\n\n\n
Happy Coding!<\/em><\/p>\n\n\n\n\n","protected":false},"excerpt":{"rendered":"
Vediamo insieme come gestire l\u2019autenticazione in una architettura a microservizi con ASP.NET Core, Angular, IdentityServer, MongoDB e Docker<\/p>\n","protected":false},"author":196716248,"featured_media":26669,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"off","_et_pb_old_content":"","_et_gb_content_width":"","_coblocks_attr":"","_coblocks_dimensions":"","_coblocks_responsive_height":"","_coblocks_accordion_ie_support":"","_crdt_document":"","inline_featured_image":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"_wpas_customize_per_network":false,"jetpack_post_was_ever_published":false},"categories":[688637374],"tags":[688637387,688637414,688637382,688637545,688637426,688637425,688637424],"class_list":["post-26667","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-angular","tag-asp-net-core","tag-c","tag-docker","tag-identityserver","tag-microservices","tag-mongdb"],"yoast_head":"\nAngular, Microservizi e Autenticazione con IdentityServer, MongoDB e Docker - Blexin<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blexin.com\/it\/blog\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\/\" \/>\n<meta property=\"og:locale\" content=\"it_IT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Angular, Microservizi e Autenticazione con IdentityServer, MongoDB e Docker - Blexin\" \/>\n<meta property=\"og:description\" content=\"Vediamo insieme come gestire l\u2019autenticazione in una architettura a microservizi con ASP.NET Core, Angular, IdentityServer, MongoDB e Docker\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blexin.com\/it\/blog\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\/\" \/>\n<meta property=\"og:site_name\" content=\"Blexin\" \/>\n<meta property=\"article:published_time\" content=\"2020-05-19T22:00:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-06-09T10:13:26+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/i1.wp.com\/blexin.com\/wp-content\/uploads\/2020\/12\/5ea7a0a4-b8a8-442f-9cdf-084c1cec81d0.png?fit=1024%2C608\" \/>\n\t<meta property=\"og:image:width\" content=\"1024\" \/>\n\t<meta property=\"og:image:height\" content=\"608\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Michele Aponte\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Scritto da\" \/>\n\t<meta name=\"twitter:data1\" content=\"Michele Aponte\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tempo di lettura stimato\" \/>\n\t<meta name=\"twitter:data2\" content=\"11 minuti\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/blexin.com\\\/it\\\/blog\\\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blexin.com\\\/it\\\/blog\\\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\\\/\"},\"author\":{\"name\":\"Michele Aponte\",\"@id\":\"https:\\\/\\\/blexin.com\\\/it\\\/#\\\/schema\\\/person\\\/cdc5540c3b6edcacd8d760669e797005\"},\"headline\":\"Angular, Microservizi e Autenticazione con IdentityServer, MongoDB e Docker\",\"datePublished\":\"2020-05-19T22:00:00+00:00\",\"dateModified\":\"2021-06-09T10:13:26+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/blexin.com\\\/it\\\/blog\\\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\\\/\"},\"wordCount\":1626,\"image\":{\"@id\":\"https:\\\/\\\/blexin.com\\\/it\\\/blog\\\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/i0.wp.com\\\/blexin.com\\\/wp-content\\\/uploads\\\/2020\\\/12\\\/5ea7a0a4-b8a8-442f-9cdf-084c1cec81d0.png?fit=1024%2C608&ssl=1\",\"keywords\":[\"Angular\",\"Asp.net core\",\"C#\",\"Docker\",\"Identityserver\",\"Microservices\",\"MongDB\"],\"articleSection\":[\"Blog\"],\"inLanguage\":\"it-IT\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/blexin.com\\\/it\\\/blog\\\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\\\/\",\"url\":\"https:\\\/\\\/blexin.com\\\/it\\\/blog\\\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\\\/\",\"name\":\"Angular, Microservizi e Autenticazione con IdentityServer, MongoDB e Docker - Blexin\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blexin.com\\\/it\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/blexin.com\\\/it\\\/blog\\\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/blexin.com\\\/it\\\/blog\\\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/i0.wp.com\\\/blexin.com\\\/wp-content\\\/uploads\\\/2020\\\/12\\\/5ea7a0a4-b8a8-442f-9cdf-084c1cec81d0.png?fit=1024%2C608&ssl=1\",\"datePublished\":\"2020-05-19T22:00:00+00:00\",\"dateModified\":\"2021-06-09T10:13:26+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/blexin.com\\\/it\\\/#\\\/schema\\\/person\\\/cdc5540c3b6edcacd8d760669e797005\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/blexin.com\\\/it\\\/blog\\\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\\\/#breadcrumb\"},\"inLanguage\":\"it-IT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/blexin.com\\\/it\\\/blog\\\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"it-IT\",\"@id\":\"https:\\\/\\\/blexin.com\\\/it\\\/blog\\\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\\\/#primaryimage\",\"url\":\"https:\\\/\\\/i0.wp.com\\\/blexin.com\\\/wp-content\\\/uploads\\\/2020\\\/12\\\/5ea7a0a4-b8a8-442f-9cdf-084c1cec81d0.png?fit=1024%2C608&ssl=1\",\"contentUrl\":\"https:\\\/\\\/i0.wp.com\\\/blexin.com\\\/wp-content\\\/uploads\\\/2020\\\/12\\\/5ea7a0a4-b8a8-442f-9cdf-084c1cec81d0.png?fit=1024%2C608&ssl=1\",\"width\":1024,\"height\":608},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/blexin.com\\\/it\\\/blog\\\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/blexin.com\\\/it\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Angular, Microservizi e Autenticazione con IdentityServer, MongoDB e Docker\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/blexin.com\\\/it\\\/#website\",\"url\":\"https:\\\/\\\/blexin.com\\\/it\\\/\",\"name\":\"Blexin\",\"description\":\"Con noi \u00e8 semplice\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/blexin.com\\\/it\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"it-IT\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/blexin.com\\\/it\\\/#\\\/schema\\\/person\\\/cdc5540c3b6edcacd8d760669e797005\",\"name\":\"Michele Aponte\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"it-IT\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/32138aff568f2063b34d27a23cef27e09f3159bfcadea5ea05599c499cf4342f?s=96&d=identicon&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/32138aff568f2063b34d27a23cef27e09f3159bfcadea5ea05599c499cf4342f?s=96&d=identicon&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/32138aff568f2063b34d27a23cef27e09f3159bfcadea5ea05599c499cf4342f?s=96&d=identicon&r=g\",\"caption\":\"Michele Aponte\"},\"url\":\"https:\\\/\\\/blexin.com\\\/it\\\/author\\\/michele-aponteblexin-com\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Angular, Microservizi e Autenticazione con IdentityServer, MongoDB e Docker - Blexin","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/blexin.com\/it\/blog\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\/","og_locale":"it_IT","og_type":"article","og_title":"Angular, Microservizi e Autenticazione con IdentityServer, MongoDB e Docker - Blexin","og_description":"Vediamo insieme come gestire l\u2019autenticazione in una architettura a microservizi con ASP.NET Core, Angular, IdentityServer, MongoDB e Docker","og_url":"https:\/\/blexin.com\/it\/blog\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\/","og_site_name":"Blexin","article_published_time":"2020-05-19T22:00:00+00:00","article_modified_time":"2021-06-09T10:13:26+00:00","og_image":[{"width":1024,"height":608,"url":"https:\/\/i1.wp.com\/blexin.com\/wp-content\/uploads\/2020\/12\/5ea7a0a4-b8a8-442f-9cdf-084c1cec81d0.png?fit=1024%2C608","type":"image\/png"}],"author":"Michele Aponte","twitter_card":"summary_large_image","twitter_misc":{"Scritto da":"Michele Aponte","Tempo di lettura stimato":"11 minuti"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blexin.com\/it\/blog\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\/#article","isPartOf":{"@id":"https:\/\/blexin.com\/it\/blog\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\/"},"author":{"name":"Michele Aponte","@id":"https:\/\/blexin.com\/it\/#\/schema\/person\/cdc5540c3b6edcacd8d760669e797005"},"headline":"Angular, Microservizi e Autenticazione con IdentityServer, MongoDB e Docker","datePublished":"2020-05-19T22:00:00+00:00","dateModified":"2021-06-09T10:13:26+00:00","mainEntityOfPage":{"@id":"https:\/\/blexin.com\/it\/blog\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\/"},"wordCount":1626,"image":{"@id":"https:\/\/blexin.com\/it\/blog\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\/#primaryimage"},"thumbnailUrl":"https:\/\/i0.wp.com\/blexin.com\/wp-content\/uploads\/2020\/12\/5ea7a0a4-b8a8-442f-9cdf-084c1cec81d0.png?fit=1024%2C608&ssl=1","keywords":["Angular","Asp.net core","C#","Docker","Identityserver","Microservices","MongDB"],"articleSection":["Blog"],"inLanguage":"it-IT"},{"@type":"WebPage","@id":"https:\/\/blexin.com\/it\/blog\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\/","url":"https:\/\/blexin.com\/it\/blog\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\/","name":"Angular, Microservizi e Autenticazione con IdentityServer, MongoDB e Docker - Blexin","isPartOf":{"@id":"https:\/\/blexin.com\/it\/#website"},"primaryImageOfPage":{"@id":"https:\/\/blexin.com\/it\/blog\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\/#primaryimage"},"image":{"@id":"https:\/\/blexin.com\/it\/blog\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\/#primaryimage"},"thumbnailUrl":"https:\/\/i0.wp.com\/blexin.com\/wp-content\/uploads\/2020\/12\/5ea7a0a4-b8a8-442f-9cdf-084c1cec81d0.png?fit=1024%2C608&ssl=1","datePublished":"2020-05-19T22:00:00+00:00","dateModified":"2021-06-09T10:13:26+00:00","author":{"@id":"https:\/\/blexin.com\/it\/#\/schema\/person\/cdc5540c3b6edcacd8d760669e797005"},"breadcrumb":{"@id":"https:\/\/blexin.com\/it\/blog\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\/#breadcrumb"},"inLanguage":"it-IT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blexin.com\/it\/blog\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\/"]}]},{"@type":"ImageObject","inLanguage":"it-IT","@id":"https:\/\/blexin.com\/it\/blog\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\/#primaryimage","url":"https:\/\/i0.wp.com\/blexin.com\/wp-content\/uploads\/2020\/12\/5ea7a0a4-b8a8-442f-9cdf-084c1cec81d0.png?fit=1024%2C608&ssl=1","contentUrl":"https:\/\/i0.wp.com\/blexin.com\/wp-content\/uploads\/2020\/12\/5ea7a0a4-b8a8-442f-9cdf-084c1cec81d0.png?fit=1024%2C608&ssl=1","width":1024,"height":608},{"@type":"BreadcrumbList","@id":"https:\/\/blexin.com\/it\/blog\/angular-microservizi-e-autenticazione-con-identityserver-mongodb-e-docker\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blexin.com\/it\/"},{"@type":"ListItem","position":2,"name":"Angular, Microservizi e Autenticazione con IdentityServer, MongoDB e Docker"}]},{"@type":"WebSite","@id":"https:\/\/blexin.com\/it\/#website","url":"https:\/\/blexin.com\/it\/","name":"Blexin","description":"Con noi \u00e8 semplice","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blexin.com\/it\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"it-IT"},{"@type":"Person","@id":"https:\/\/blexin.com\/it\/#\/schema\/person\/cdc5540c3b6edcacd8d760669e797005","name":"Michele Aponte","image":{"@type":"ImageObject","inLanguage":"it-IT","@id":"https:\/\/secure.gravatar.com\/avatar\/32138aff568f2063b34d27a23cef27e09f3159bfcadea5ea05599c499cf4342f?s=96&d=identicon&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/32138aff568f2063b34d27a23cef27e09f3159bfcadea5ea05599c499cf4342f?s=96&d=identicon&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/32138aff568f2063b34d27a23cef27e09f3159bfcadea5ea05599c499cf4342f?s=96&d=identicon&r=g","caption":"Michele Aponte"},"url":"https:\/\/blexin.com\/it\/author\/michele-aponteblexin-com\/"}]}},"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/blexin.com\/wp-content\/uploads\/2020\/12\/5ea7a0a4-b8a8-442f-9cdf-084c1cec81d0.png?fit=1024%2C608&ssl=1","jetpack_shortlink":"https:\/\/wp.me\/pcyUBx-6W7","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/blexin.com\/it\/wp-json\/wp\/v2\/posts\/26667","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blexin.com\/it\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blexin.com\/it\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blexin.com\/it\/wp-json\/wp\/v2\/users\/196716248"}],"replies":[{"embeddable":true,"href":"https:\/\/blexin.com\/it\/wp-json\/wp\/v2\/comments?post=26667"}],"version-history":[{"count":14,"href":"https:\/\/blexin.com\/it\/wp-json\/wp\/v2\/posts\/26667\/revisions"}],"predecessor-version":[{"id":33046,"href":"https:\/\/blexin.com\/it\/wp-json\/wp\/v2\/posts\/26667\/revisions\/33046"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blexin.com\/it\/wp-json\/wp\/v2\/media\/26669"}],"wp:attachment":[{"href":"https:\/\/blexin.com\/it\/wp-json\/wp\/v2\/media?parent=26667"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blexin.com\/it\/wp-json\/wp\/v2\/categories?post=26667"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blexin.com\/it\/wp-json\/wp\/v2\/tags?post=26667"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}