DDT.Packages.InBoundAuthorization 1.3.2

In Bound Authorization

Flow

• The gateway verifies the token is valid against the identity API
• It requests the user id, email and roles from the Auth API
• The gateway uses our package to add a header with the encoded data
• it sends the encoded data to the service
• the service uses our package authorization scheme to validate the roles
• it's compatible with the regular authorization flow so there is no learning curve or anything different

Usage

Issuer Side

• install dotnet add package DDT.Packages.InBoundAuthorization --version 1.3.2
• add context.Request.Headers.AddDDTInBoundAuthorization(new DDTInBoundAuthToken([user.Id](http://user.id/), user.Email, user.Roles)); wherever you want to inject the token into the headers

Resource Side

• install dotnet add package DDT.Packages.InBoundAuthorization --version 1.3.2

• in your program.cs

  • add

  builder.Services.AddAuthentication(DDTInBoundAuth.Scheme).AddDDTInBoundAuthorization();
  

  • add

  app.UseAuthentication();
  
  app.UseAuthorization();
  

• in your controller

  • add

  [Authorize(Roles ="roleName")]