<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with header]]></title><description><![CDATA[A list of topics that have been tagged with header]]></description><link>https://fusionauth.io/community/forum/tags/header</link><generator>RSS for Node</generator><lastBuildDate>Mon, 17 Aug 2026 05:26:18 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/tags/header.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[fusion auth versus jose4j library for jwt using secp256k]]></title><description><![CDATA[
ok main thing is, is it ok to use header ES256 for jwt created using secp256k1 keys?

<p dir="auto"><a href="https://datatracker.ietf.org/doc/html/rfc8812" rel="nofollow ugc">https://datatracker.ietf.org/doc/html/rfc8812</a> says, secp256k1 curve should only be used with ES256k header, but in authfusion even if we give k1 pair keys and then use sign and encode a JWT using EC, it will come as ES256 only, is that okay?</p>

Another doubt is, those jwt (k1 curve keys + ES256) created in authfusion is only able to verify in jose4j with .setRelaxVerificationKeyValidation() //needed if the key is smaller than 256 bits.

<p dir="auto">Without it we get the error:</p>
JWT processing failed. Additional details: &lsqb;&lsqb;17] Unable to process JOSE object (cause: org.jose4j.lang.InvalidKeyException: ES256/SHA256withECDSA expects a key using P-256 but was null):

<p dir="auto">Description inside <strong>setRelaxVerificationKeyValidation</strong> :</p>
Bypass the strict checks on the verification key. This might be needed, for example, if the JWT issuer is using 1024-bit RSA keys or HMAC secrets that are too small (smaller than the size of the hash output)

<p dir="auto">Is it the correct way to validate jwt created using ec in authfusion?</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2315/fusion-auth-versus-jose4j-library-for-jwt-using-secp256k</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2315/fusion-auth-versus-jose4j-library-for-jwt-using-secp256k</guid><dc:creator><![CDATA[benjamineroommen]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Do you support adding headers to the fusionauth generated jwt]]></title><description><![CDATA[<p dir="auto">No, FusionAuth doesn't support adding JWT headers to FusionAuth generated JWTs. I looked at the code and don't think it'd be a ton of work to add support; there's already some scaffolding in the fusionauth-jwt OSS project.</p>
<p dir="auto">I highly encourage anyone with this problem to file a feature request here with more details about your needs: <a href="https://github.com/fusionauth/fusionauth-issues/issues" rel="nofollow ugc">https://github.com/fusionauth/fusionauth-issues/issues</a></p>
<p dir="auto">We consult that in our roadmap planning. We also offer professional services if you need us to build it on a schedule. Please send a request to <a href="https://fusionauth.io/contact" rel="nofollow ugc">our sales department</a> if that is an option you'd like to pursue.</p>
<p dir="auto">An alternative would be to build a service that would re-sign your JWTs from FusionAuth with the needed header changes. Not optimal, I understand, but another avenue that might get you what you need.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/966/do-you-support-adding-headers-to-the-fusionauth-generated-jwt</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/966/do-you-support-adding-headers-to-the-fusionauth-generated-jwt</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>