How to invalidate cache of RemoteJWKSet in nimbus-jose-jwt












0















We are making use of RemoteJWKSet in nimbus-jose-jwt third party library for JWKS endpoint based JWT validation.



With RemoteJWKSet, we can retrieve the JWKS from a remote endpoint and the retrieved JWK set is cached in order to to minimize network calls.
Also it is capable of handling key rotation at the remote server since the cache is updated whenever the key selector tries to get a key with an unknown KID.



My question is that, let's say a particular key set is removed from the remote JWKS endpoint due to security reasons. But when we get a JWT that was signed using the removed key, it will still be valid since that keyset is available in the cache (RemoteJWKSet will only update the cache when it gets a token with an unknown KID).



I need to know is there any possible way to invalidate the cached JWK set in RemoteJWKSet if required other that restarting the server?










share|improve this question



























    0















    We are making use of RemoteJWKSet in nimbus-jose-jwt third party library for JWKS endpoint based JWT validation.



    With RemoteJWKSet, we can retrieve the JWKS from a remote endpoint and the retrieved JWK set is cached in order to to minimize network calls.
    Also it is capable of handling key rotation at the remote server since the cache is updated whenever the key selector tries to get a key with an unknown KID.



    My question is that, let's say a particular key set is removed from the remote JWKS endpoint due to security reasons. But when we get a JWT that was signed using the removed key, it will still be valid since that keyset is available in the cache (RemoteJWKSet will only update the cache when it gets a token with an unknown KID).



    I need to know is there any possible way to invalidate the cached JWK set in RemoteJWKSet if required other that restarting the server?










    share|improve this question

























      0












      0








      0








      We are making use of RemoteJWKSet in nimbus-jose-jwt third party library for JWKS endpoint based JWT validation.



      With RemoteJWKSet, we can retrieve the JWKS from a remote endpoint and the retrieved JWK set is cached in order to to minimize network calls.
      Also it is capable of handling key rotation at the remote server since the cache is updated whenever the key selector tries to get a key with an unknown KID.



      My question is that, let's say a particular key set is removed from the remote JWKS endpoint due to security reasons. But when we get a JWT that was signed using the removed key, it will still be valid since that keyset is available in the cache (RemoteJWKSet will only update the cache when it gets a token with an unknown KID).



      I need to know is there any possible way to invalidate the cached JWK set in RemoteJWKSet if required other that restarting the server?










      share|improve this question














      We are making use of RemoteJWKSet in nimbus-jose-jwt third party library for JWKS endpoint based JWT validation.



      With RemoteJWKSet, we can retrieve the JWKS from a remote endpoint and the retrieved JWK set is cached in order to to minimize network calls.
      Also it is capable of handling key rotation at the remote server since the cache is updated whenever the key selector tries to get a key with an unknown KID.



      My question is that, let's say a particular key set is removed from the remote JWKS endpoint due to security reasons. But when we get a JWT that was signed using the removed key, it will still be valid since that keyset is available in the cache (RemoteJWKSet will only update the cache when it gets a token with an unknown KID).



      I need to know is there any possible way to invalidate the cached JWK set in RemoteJWKSet if required other that restarting the server?







      jwt nimbus jwk jose






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 26 '18 at 9:46









      sathyasathya

      26819




      26819
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Raised the same question at connect2id support portal [1]



          They have suggested to put an empty JWK set which will cause the RemoteJWKSet to reload the key set from the URL on the next call as a mechanism to invalidate the JWKS cache.



          [1] https://bitbucket.org/connect2id/nimbus-jose-jwt/issues/287/how-to-invalidate-cache-of-remotejwkset-in






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53478379%2fhow-to-invalidate-cache-of-remotejwkset-in-nimbus-jose-jwt%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Raised the same question at connect2id support portal [1]



            They have suggested to put an empty JWK set which will cause the RemoteJWKSet to reload the key set from the URL on the next call as a mechanism to invalidate the JWKS cache.



            [1] https://bitbucket.org/connect2id/nimbus-jose-jwt/issues/287/how-to-invalidate-cache-of-remotejwkset-in






            share|improve this answer




























              0














              Raised the same question at connect2id support portal [1]



              They have suggested to put an empty JWK set which will cause the RemoteJWKSet to reload the key set from the URL on the next call as a mechanism to invalidate the JWKS cache.



              [1] https://bitbucket.org/connect2id/nimbus-jose-jwt/issues/287/how-to-invalidate-cache-of-remotejwkset-in






              share|improve this answer


























                0












                0








                0







                Raised the same question at connect2id support portal [1]



                They have suggested to put an empty JWK set which will cause the RemoteJWKSet to reload the key set from the URL on the next call as a mechanism to invalidate the JWKS cache.



                [1] https://bitbucket.org/connect2id/nimbus-jose-jwt/issues/287/how-to-invalidate-cache-of-remotejwkset-in






                share|improve this answer













                Raised the same question at connect2id support portal [1]



                They have suggested to put an empty JWK set which will cause the RemoteJWKSet to reload the key set from the URL on the next call as a mechanism to invalidate the JWKS cache.



                [1] https://bitbucket.org/connect2id/nimbus-jose-jwt/issues/287/how-to-invalidate-cache-of-remotejwkset-in







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 27 '18 at 9:07









                sathyasathya

                26819




                26819
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53478379%2fhow-to-invalidate-cache-of-remotejwkset-in-nimbus-jose-jwt%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

                    Calculate evaluation metrics using cross_val_predict sklearn

                    Insert data from modal to MySQL (multiple modal on website)