kalpana_seagate
Occasional Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: ccollab admin review set-participants doesn't work if user id is in digits
Hi Oleg, I rolled back the client to Version 9.1.9101 and tested some commands and they are working fine on test machine. Will run some more test and roll back client on production machine. Thanks for your help. Regards, Kalpana2.8KViews0likes0Commentsccollab admin review set-participants doesn't work if user id is in digits
When the user name contains digits the ccollab set-setparticipants doesn't work, but the same works if user name has only alphabets. see error below, ccollab admin review set-participants 1593 --participant Author=524975 Connecting to server at http://localhost Connected to Collaborator Enterprise v10.0.10000 Connected as: Kalpana Manoharan (524975) ERROR: Executing command `ccollab admin review set-participants`: Errors found: [ { "result" : { } }, { "result" : { } }, { "errors" : [ { "code" : "InvalidUser", "message" : "Invalid User 524975" } ] } ] ===================================================================================== ccollab admin review set-participants 1593 --participant Author=codereview Connecting to server at http://localhost Connected to Collaborator Enterprise v10.0.10000 Connected as: Kalpana Manoharan (524975) Set 1 assignments Note: The users are LDAP authenticated. Please help in resolving the issue Regards, KalpanaSolved2.9KViews0likes5CommentsRe: After LDAP upgrade, command line ccollab login <url> <user> <password> doesn't work
I upgraded to latest version and the ccollab login is successful. But I'm getting an error when i try to set the participants for the existing review using command. Error log below, ccollab admin review set-participants 1593 --participant Author=524975 Connecting to server at http://localhost Connected to Collaborator Enterprise v10.0.10000 Connected as: Kalpana Manoharan (524975) ERROR: Executing command `ccollab admin review set-participants`: Errors found: [ { "result" : { } }, { "result" : { } }, { "errors" : [ { "code" : "InvalidUser", "message" : "Invalid User 524975" } ] } ] Regards, Kalpana3.4KViews0likes1CommentRe: After LDAP upgrade, command line ccollab login <url> <user> <password> doesn't work
Can we have a temporary fix for this issue or a patch? We have rational clearquest integrated with code collab through command line and this issue is blocking the review creation. And also please let me know the release date for next version. Regards, Kalpana3.4KViews0likes2CommentsAfter LDAP upgrade, command line ccollab login <url> <user> <password> doesn't work
After LDAP configuration and version upgrade, command line doesn't work. ccollab login http://codecollaborator 524975 jsdsjdjs throws an error, ERROR: Connectivity problem with Collaborator server: Unexpected Error: com.smartbear.jsonrpc.impl.JsonRequestException: Errors found: [ { "result" : { } }, { "errors" : [ { "code" : "InvalidAuthentication", "message" : "Your ticket is invalid. Please try to login and then reattempt this command." } ] } ] You may need to run 'ccollab login' to verify your configuration settings But when the command is run without passing user name and password, it prompts for the information and the same user, password works fine. C:\>ccollab login http://codecollaborator Please enter your username: (default: 524975) > 524975 Please enter your password: (Input will not echo.) Trying to login with new configuration Connecting to Collaborator Server http://codecollaborator Connected as: Kalpana Manoharan (524975) New configuration worked - saving configuration settings Configuration key 'url' saved. Configuration key 'user' saved. Configuration key 'server-proxy-host' cleared. Configuration key 'server-proxy-port' cleared.. The password does not have any special characters (only alphabets and numbers). I tried with single quote, double quote, but nothing works. I need this because we have some inhouse scripts which will invoke collab commands. Any help appreciated. thanks.3.5KViews0likes6Comments