In this post, I am going to continue my series about IdenityServer4. I will write about forcing IdentityServer to use Google as an external identity token provider. Before I started, I had to register the application that will interact with Google which in my case is IdSrvHost. I am going to reuse the application that I registered in this post. However, I altered the configuration of this application a bit by enabling access to Google+ API.…
In the previous post, I wrote about how to get tokens from IdentityServer using a javascript client. In this post, I am going to write about how to use this token to get access to protected resources from a sample API. As in the previous post, to achieve my goal, I used samples provided on the github repository. In this repo folder I found a sample API which I copied into my local repository.…
I wrote in one of previous posts about my experiments with Google Identity Provider and Implicit Flow to get access tokens which allow me to fetch resources from API. I didn’t mention IdentityServer IdentityServer in these posts, which is becoming the default choice if you want to create an identity provider in ASP .NET. I did this deliberately because I had some experiences with IdentityServer 3 and I wanted to try something new.…
In the previous post, I wrote about accessing a protected API controller being authenticated with id tokens obtained from Google. I created my application on Windows in Visual Studio because I needed the helping hand of dotPeek to see what was going on inside code that is not mine. In this post, I’ll write what happened when I ran this application on Ubuntu. After I pulled my project from github, I restored all packages using dnu restore and I ran the application.…
In previous posts I wrote about getting id tokens and access tokens from Google Identity Provider. To do this I used the library oidc-token-manager. You can read here and here how I prepared config for this library in order to have a working authentication of a user in Google Identity Provider. I stated that my solution isn’t perfect and actually I treated it as a temporary one. In this post, I’ll write about using tokens fetched from Google to access my sample API.…
This post is a continuation of the previous one previous one where I started to describe my attempt to use library oidc-token-manager with Google Identity Platform. I was stuck at the moment when this library couldn’t validate a signature for an access token because of the unexpected format of the certs. I found in the documentation that I can provide certs for this library myself in the config and the library wouldn’t make a request for them.…
As I stated in this post, I am going to write a series of posts about auth stuff. This post will be the second in this series and I am describing my experiences trying to use the library oidc-token-manager to get tokens from the Google Identity Platform. As I mentioned before, I want to have a single page application which gets tokens from Identity Provider and sends them to REST API to get access to resources.…
Recently, I thought about a membership system in my application. I considered many options and during my research I tested many solutions, and gained some knowledge. The results from my initial search didn’t pan out as planned, so I’ll have to share my results in a series of posts, and this post will be part one. One of my ideas was not having a membership system at all and delegating this to a well known identity provider like Google or Facebook.…