GenericTokenExtractor 1.0.0

GenericTokenExtractor

A lightweight .NET package that provides an easy way to access tokens (such as JWTs) from the current HttpContext in ASP.NET Core applications.
It is designed to be simple, dependency-injected, and ready to use.

📦 Installation

You can install the package via NuGet:

dotnet add package GenericTokenExtractor --version <version>

Or via the Visual Studio NuGet Package Manager.

🚀 Getting Started

1. Register the GenericTokenExtractor in your Startup / Program.cs

using Microsoft.Extensions.DependencyInjection;
using GenericTokenExtractor;

public class Startup
{
    public void ConfigureServices(IServiceCollection services)
    {
        // Add GenericTokenExtractor service
        services.GenericTokenExtractor();
        
        // Other services
    }
}

This extension method will register:

• IHttpContextAccessor (required to access the current HttpContext)
• IGenericTokenExtractor for resolving tokens

2. Inject and Use the IGenericTokenExtractor

You can now inject IGenericTokenExtractor into any service or controller.

using Microsoft.AspNetCore.Mvc;
using GenericTokenExtractor;

[ApiController]
[Route("api/[controller]")]
public class SampleController : ControllerBase
{
    private readonly IGenericTokenExtractor _tokenProvider;

    public SampleController(IGenericTokenExtractor tokenProvider)
    {
        _tokenProvider = tokenProvider;
    }

    [HttpGet("user-token")]
    public IActionResult GetUserToken()
    {
        var token = _tokenProvider.GetToken();
        if (string.IsNullOrEmpty(token))
            return Unauthorized("No token found");

        return Ok(new { Token = token });
    }
}

🔧 Features

• ✅ Provides a clean abstraction IGenericTokenExtractor
• ✅ Automatically retrieves tokens from Authorization header in HttpContext
• ✅ Works with JWT Bearer tokens and custom headers
• ✅ Easy to integrate via Dependency Injection
• ✅ Minimal setup required

❓ FAQ (For Consumers)

Q: Do I need to manually add IHttpContextAccessor?
No, AddGenericTokenExtractor() automatically registers it for you.

Q: Where does the GenericTokenExtractor fetch the token from?
By default, it looks for the Authorization header in the current HttpContext.

Q: What if there’s no token present?
The GetToken() method will return null or an empty string. You can handle it as per your app’s requirements.

Q: Can I use it outside of ASP.NET Core apps?
Not directly — it depends on HttpContext. However, you can adapt it for background services that run within the ASP.NET Core host.

Q: Does it validate or decode the token?
No, this package only retrieves the token. Validation/decoding should be handled separately (e.g., using Microsoft Identity packages or JWT libraries).

🛠 Example Usage in a Service

public class MyBusinessService
{
    private readonly IGenericTokenExtractor _tokenProvider;

    public MyBusinessService(IGenericTokenExtractor tokenProvider)
    {
        _tokenProvider = tokenProvider;
    }

    public void DoWork()
    {
        var token = _tokenProvider.GetToken();
        Console.WriteLine($"Token: {token}");
    }
}

📌 Versioning

This package follows semantic versioning.
Breaking changes will be introduced in major versions (1.x → 2.x).

🤝 Contributing

Contributions are welcome!
Please fork the repository and create a pull request.

📄 License

This project is licensed under the MIT License - see the LICENSE file for details.