What does the password file for the lscm login option --password-file have to look like?
Balz Guenat (15●1●3)
| asked Oct 10 '18, 9:26 a.m.
retagged Oct 23 '18, 4:17 p.m. by Ken Tessier (841●1●7)
I can't find any documentation on this.
I tried just writing the PW into the file. That gives me a decoding error because of a `$` character in the PW.
I tried generating a password file as described here. That also resulted in a decoding error.
I then tried only using the PW string from aforementioned file. That didn't work either.
I saw that the decoding error came from Base64.decode() so I tried to encode the PW in Base64. That also didn't work.
|
Accepted answer
David Lafreniere (4.8k●7)
| answered Oct 10 '18, 10:06 a.m.
FORUM MODERATOR / JAZZ DEVELOPER edited Oct 11 '18, 10:00 a.m.
This feature was added in RTC 6.0.3 in Provide a way to login using CLI by specifying password encrypted file and not the password itself (295660)
Per the help documentation: https://www.ibm.com/support/knowledgecenter/en/SS2L6K_6.0.6/com.ibm.team.scm.doc/topics/login.html
-You would use 'scm login --generatePasswordFile <path_to_file>' to first generate the password file.
-Then once generated, this file can be re-used at any time using 'scm login --password-file <path_to_file>'.
This password file is encrypted, and thus we do not allow users to create it by 'hand' (which would defeat the purpose of encoding it in the first place).
Balz Guenat selected this answer as the correct answer
Comments Thank you! Your second link seems broken but I found the documentation of the --generatePasswordFile option here. I guess I just looked at the documentation of the wrong version. (Maybe a prominent hint in outdated documentation would be a good idea.)
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.