[JIRA] (JENKINS-37837) Regression: JWT token not present when logged in on blueocean.io

[vivek.pan...@gmail.com (JIRA)]

Title: Message Title

Vivek Pandey commented on JENKINS-37837   Re: Regression: JWT token not present when logged in on blueocean.io As mentioned above, the main issue was setting JWT specific Authentication object was not liked by github auth plugin, GithubRequireOrganizationMembershipACL.hasPermission(Permission) had: if (a != null && a instanceof GithubAuthenticationToken) { if (!a.isAuthenticated()) return false; }else{ return false; } While gthub auth plugin is ok to have such uses, and there might be other plugins that might enforce using their own Authentication implementation. For this reason, this fix changed how Authentication instance is created and set on SecurityContext. We define JwtAuthenticationStoreFactory extension point and JwtAuthenticationStore abstraction to store Authentication in jwt token and also to re-create Authentication instance using jwt claims. There is default implementation that use in memory map to store authentication implementation. PR is in https://github.com/jenkinsci/blueocean-plugin/pull/457 Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.