# Removing Blue Ocean credentials security vulnerability **URL:** \ **Category:** Ask a question\ **Created:** [May 26, 2022, 1:51pm UTC](https://community.jenkins.io/t/removing-blue-ocean-credentials-security-vulnerability/2554 "2022-05-26T13:51:30Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![antonio-petricca](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/antonio-petricca/32/1573_2.png) [@antonio-petricca](https://community.jenkins.io/u/antonio-petricca)\ **Post date:** [May 26, 2022, 1:51pm UTC](https://community.jenkins.io/t/removing-blue-ocean-credentials-security-vulnerability/2554/1 "2022-05-26T13:51:30Z")
Hi Guys, this is my first post. Today I updated Jenkins (Docker version) for my company as usual by the plugins update control panel. Unfortunately it broke my system due to the not announced (by the control panel itself) issue [https://support.cloudbees.com/hc/en-us/articles/5988645160219](https://support.cloudbees.com/hc/en-us/articles/5988645160219) . My comment on the above article is pending for approval, but I wish to share it here to get additional help from this community. Here is the comment text: > Hi, we use Jenkins for complex company development processes. > > We keep it updated regularly. Unfortunately this upgrade broke our systems, so we had to restore it by the most recent backup. > > Our pipelines use SSH generated keys, by the builtin credential folder “BlueOcean Folder Credentials”. > > After upgrading Jenkins that folder disappeared, and we could not select anything else. > > In order to let us, and I suppose many other companies, to upgrade Jenkins, we kindly ask you to consider one of the following proposals: > > Don’t remove the plugin in the future and let it enabled by default. Unfortunately we cannot recreate the Jenkins container in order to pass the option to enable again the provider. This is the reason why we keep it upgraded by the upgrade Jenkins menù option. > Provide a way to migrate automagically the pipelines to the new security model without any production breaking. > > In the meanwhile we don’t go further with next upgrades! ☹ ---
**Author:** ![halkeye](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/halkeye/32/8_2.png) [@halkeye](https://community.jenkins.io/u/halkeye)\ **Post date:** [May 26, 2022, 9:12pm UTC](https://community.jenkins.io/t/removing-blue-ocean-credentials-security-vulnerability/2554/2 "2022-05-26T21:12:16Z")
Cloudbees is an independent vendor and we have no say in what gets approved or not or how thier website works. I think @MarkEWaite gave you (or someone asking a similar question) some tips on gitter. Mark says > [@](#): > > Was announced on the updates control panel as the Blue Ocean plugins needing a security fix. See [Jenkins Security Advisory 2022-05-17](https://www.jenkins.io/security/advisory/2022-05-17/#SECURITY-714) for the notes about the fix and for alternatives if you need an “escape hatch” In addition, blueocean has been pretty much abandoned for many years now. Only security updates really get updated. (and some random things cloudbees pushes for thier customers). I recommend strongly moving away from blue ocean. There’s a couple replacement plugins that bring in some of the functionality into classic view. I know the pipeline generator and thus credentials are not migrated and afaik no intention to be migrated. ---
**Author:** ![antonio-petricca](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/antonio-petricca/32/1573_2.png) [@antonio-petricca](https://community.jenkins.io/u/antonio-petricca)\ **Post date:** [May 27, 2022, 9:56am UTC](https://community.jenkins.io/t/removing-blue-ocean-credentials-security-vulnerability/2554/3 "2022-05-27T09:56:25Z")
Thank you so much for your support. At the moment we cannot move away from BlueOcean, and we don’t want to keep our Jenkins outdated. Could you tell us how to migrate credentials as introduced by the official Cloudbees link?