humm.. I deleted identity.key and secret.key, restarted jenkins, and tried again: the two files have been recreated, but got the same error!
Any more hints, please? 2012/5/2 Jan Seidel <wakkal...@gmail.com> > Hi Nunni, > > *uhm* only thing that crosses my mind is a buggy identity.key file or > secret.key file. The secret.key is more likely to fail. > You can rebuild it somewhat easy. simply delete the secret.key files. They > are located in the jenkins root folder and in the job folders. > They contain the encryption key to garble/ungarble the credentials you > have saved in Jenkins. Only garbage will be send as response if this key > file is out of sync with Jenkins. > > You will have to re-enter passwords in your configuration as the will > definitely become unvalid when the key file is missing. > So lucky you if the credentials for your repository and the like are > stored globally in "Manage Jenkins" and not individually by job. Good time > to change it if the later case just comes back on you ;) > > > Am Mittwoch, 2. Mai 2012 11:11:04 UTC+2 schrieb Nunni: > >> Hi Jan. >> Sorry for not replying earlier.. I was on holiday and got back to work >> only this morning. >> >> No.. no special characters that need to be escaped, nor wrong password.. >> I even tried copy/paste of the password, but it doesn't help.. >> >> Any more hints, please? >> >> >> 2012/4/30 Jan Seidel <wakkal...@gmail.com> >> >>> >>> Hi Nunni, >>> >>> org.acegisecurity.**BadCredentialsException: Bad credentials tells you >>> at least that something is happening and then fails. This looks more like a >>> matter of human engineering rather the technical engineering ;) >>> Do you use some funny special character which may interfere with your >>> system/shell/CLI. You will then have to escape the characters in question >>> or evene better select a passwort less prone to error. >>> >>> @David: "By the way, what are you doing with the command line? Jenkins >>> is a purely web-based application, and the configuration is carried out via >>> the webpage." ??? >>> How did tell you that? The web based part is just a convenience thingy. >>> >>> You can run it from command line without webfront. I do more and more >>> rarely use the webfront and run the administrative task straight from the >>> operating systems CLI >>> Further does Jenkins also provide it's own CLI (see: >>> http://jenkins_server/cli) >>> >>> Take care >>> Jan >>> >>> >>
