Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-73491

GCP secret manager doesn't allow special characters in labels

XMLWordPrintable

      In case the secret should be stored as a username and password, the username should be specified in a secret label but if the username contains the @ sign it isn't allowed in the gcp secret manager label.

      Today usernames in the email format are very common so that limitation is the blocker,

      Suggestion : store the username as the secret annotation instead of the label. 

          [JENKINS-73491] GCP secret manager doesn't allow special characters in labels

          Alex added a comment -

          markewaite I know that's exactly the problem.

          Todays we have many systems which expect to accept the user name in the email format (with @) . So I can't use the GCP secret manager for storing credentials for these systems so Jenkins will be using them in its jobs.

          Today I must store these credentials in other stores ( for example in the jenkins internal store) just because I can't write the user name with @ in the gcp secret label 

          Alex added a comment - markewaite I know that's exactly the problem. Todays we have many systems which expect to accept the user name in the email format (with @) . So I can't use the GCP secret manager for storing credentials for these systems so Jenkins will be using them in its jobs. Today I must store these credentials in other stores ( for example in the jenkins internal store) just because I can't write the user name with @ in the gcp secret label 

          Mark Waite added a comment -

          Thanks alexku7. The comment that prompted your reply was written by someone else and included a spam link that is unrelated to Jenkins. I deleted the comment and disabled the account of the user that posted the spam link.

          Mark Waite added a comment - Thanks alexku7 . The comment that prompted your reply was written by someone else and included a spam link that is unrelated to Jenkins. I deleted the comment and disabled the account of the user that posted the spam link.

          Bartosz Nowak added a comment -

          Maybe we can make it work by adding unicode encoding? and then inside plugin it will be decoded?

          Bartosz Nowak added a comment - Maybe we can make it work by adding unicode encoding? and then inside plugin it will be decoded?

            mdaugherty6 Michael Daugherty
            alexku7 Alex
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: