• Products
    • IdentityServer
    • IdentityServer for Redistribution
    • Backend for Frontend (BFF) Security Framework
  • Documentation
  • Training
  • Resources
    • Company Blog
    • Featured Articles
    • About
      • Company
      • Partners
      • Careers
      • Contact
    Duende Software Blog
    • Products
      • IdentityServer
      • IdentityServer for Redistribution
      • Backend for Frontend (BFF) Security Framework
      • Open Source
    • Documentation
    • Training
    • Resources
      • Company Blog

        Stay up-to-date with the latest developments in identity and access management.

      • Featured Articles
      • About
        • Company
        • Partners
        • Careers
        • Contact
      • Start for free
        Contact sales

      Pushed Authorization Request (PAR) Support in ASP.NET Core

      Damian Hickey Chief Architect & Director of Engineering at Duende Software Damian Hickey

      published on September 5, 2024

      We think that PAR is one of the easiest ways to increase the security of OAuth and OpenID Connect. That’s why we prioritized the implementation of the RFC and released fully featured support in IdentityServer v7.

      Unfortunately, it wasn’t as straightforward as it could be to add client-side PAR support to an existing ASP.NET Core application using the Microsoft OpenID Connect authentication handler.

      While the OIDC handler is general very well factored and provides extensibility points to accommodate a wide range of protocol extensions that haven’t even existed when the handler was written, for this particular scenario, it was lacking the right granularity. We have a sample here that adds PAR support, but unfortunately some of the OIDC handler internals had to be replicated.

      We are happy to announce that starting with .NET 9, the ASP.NET Core OIDC handler will have built-in PAR support. Even further, the current previews of .NET 9 have PAR enabled by default. This means every application gets the new security feature by default if the OIDC provider supports it. That’s huge.

      This feature was contributed by our IdentityServer lead Joe DeCock. See here and here for his blog posts diving into the technical details.

      Thanks Joe for making ASP.NET more secure!

      Duende logo

      Products

      • IdentityServer
      • IdentityServer for Redistribution
      • Backend for Frontend (BFF)
      • IdentityModel
      • Access Token Management
      • IdentityModel OIDC Client

      Community

      • Documentation
      • Company Blog
      • GitHub Discussions

      Company

      • Company
      • Partners
      • Training
      • Quickstarts
      • Careers
      • Contact

      Subscribe to our newsletter

      Stay up-to-date with the latest developments in identity and access management.

      Copyright © 2020-2025 Duende Software. All rights reserved.

      Privacy Policy | Terms of Service