Migrating Code Collaborator To SAML Authenticaiton
I'm working with an existing Code Collaborator installation that has years' worth of code review records and their associated users. For security and to unify the service login procedures among several applications we use, I would like to use the SAML authentication feature of Code Collaborator. I read through the SAML single sign on documentation Smartbear provides, but I have not found any information on how adding SSO impacts existing user accounts. Does anyone have experience migrating an existing Collaborator userbase to SSO? Is there any documented steps on how I would need to perform such a migration and ensure SSO users link to their old accounts?Solved2.4KViews0likes4CommentsAccessing internalCustomFields for Triggers in Collaborator
Hello world, I can use the http://collaborator.server/services/json/v1 API with the following JSON body to get data about a review. [ { "command" : "ReviewService.findReviewById", "args" : { "reviewId" : "42" } }] Specifically, it includes the following internalCustomFields key: "internalCustomFields" : [ { "name" : "JiraIssueId", "value" : [ "10600" ] }, { "name" : "ExternalTaskId", "value" : [ "" ] } ] I would like to use this JiraIssueId field for a review as an argument to one of the configurable Triggers (say Review Phase Changed for example). Does anyone know how I would access this internal field? I know I can use ${review.custom.foo} for visible custom fields that I create, but the internal custom fields are not documented in the http://collaborator.server/manual/index.html?admin_var_subst.html documentation. I've tried ${review.internal.JiraIssueId}, ${review.internalCustomFields.JiraIssueId}, and ${review.custom.JiraIssueId} but none of them work (giving me the following error) Error: Invalid input: Parameters: ${review.internalCustom.JiraIssueId} is not a valid substitution keyword Thanks for any help! Best, ~Chris2KViews0likes1CommentSSO with ADFS Setup
Hello there! I just did a fresh install and created a new local user/login called "mjordan". My AD domain uses the same format as "mjordan". I setup the ADFS and Collaborator settings and in the first shot I did I was able to login but it did not assume the local user and instead of that looks like a new user was created called "michael.jordan@email.com". I've tried different and many Claim Rules but not working to authenticate being the local user "mjordan". Is there any other documentation in how to setup this for ADFS? Thanks! DiegoSolved1.3KViews0likes1CommentHow to start Collaborator automatically after reboot on RHEL 7
Hello, I am fairly new to Linux and I need to set up our Collaborator instance to start automatically after a reboot. We are using Red Hat Enterprise Linux 7.9 and I can't figure out how to achieve this, I see in the documentation:https://support.smartbear.com/collaborator/faq/how-to-configure-the-collaborator-server-to-start/ that there is a very brief mention on how to do this: The installation directory of the Collaborator server contains the "ccollab-server" file that can accept the usual "start" and "stop" commands. You can create a symbolic link to this file from your standard installation directory to force the server to start automatically upon system startup. I have tried creating this link in /etc/systemd/system but doesnt seem to do anything, I tried create a basic script that just calls /PathToApplication/ccollab-server start and that does not work. I tried creating a .service file which executes ccollab-server start. I can't find any helpful errors on the host and whenever I never see any entries in the collaborator error log, if i would at least get errors I could validate that my script was at least attempting to start the service. Is there anymore guidance on this other than what is in that documentation, a step by step guide or video? Thanks, feeling dumb!Solved1.2KViews0likes2Commentscreate-review post commit hook - password management and participants
Hello Is there any tutorial on how to get this working in a production environment? Especially useful would be some hints on how: 1. the hook should manage the required passwords ( ccollab-admin-trigger-create-review) (we use LDAP). 2.we can control the participants of the review (ie. like a per-user or per-source branch template?I imagine this could be done with some "custom scripting" but since it's probably a very popularrequest is there some built-in support or best practice?)995Views0likes1Commentinstall script varfile for automated install
hello, Does anyone know the format for the `varfile` flag when installing Collaborator? is this key/value? what are the keys and accepted values? Is there a sample file ? We are using linux. If we pass -q the install proceeds and does a default local install, however we are looking to automate this end to end. $ sudo ./ccollab_server.sh -h Starting Installer ... The following command line options are available: -varfile [file] Use a response file -c Run in console mode -q Run in unattended mode -dir [directory] In unattended mode, set the installation directory -overwrite In unattended mode, overwrite all files -splash [title] In unattended mode, show a progress window -Dname=value Set system properties -h Show this help928Views0likes1CommentCollaborator URL in participant notification message
After creating a new review, participants are notified via an email message stating, "Select this link to display or participate in the review: <URL>" In our environment, at least, the URL seems to be a loopback and does not take participants to the actual review package. Is there a way to configure the outgoing notification email so that it contains a link to the actual review?Solved882Views0likes1CommentMigration of user accounts to new machine?
I've been playing with Collaborator off and on. I had v10.2.10200 installed, and wanted to move it to another machine and run v13. I first upgraded the old machine to v13 and then copied thecollaborator-content-cache folder to the new machine. But when I tried to log in on the new machine, it didn't recognize my credentials. I suppose that the user accounts are stored elsewhere (I'm not using LDAP, this is just a very basic test installation), but the only information I can find online mentions copying thecollaborator-content-cache folder. Can anyone please tell me how I can get my existing user account on the old machine migrated?879Views0likes2CommentsHow to retrieve archived reviews
We recently updated to rev 13.4 of Collaborator which allows for easier archiving and possible retrieval of reviews. For the initial setup of the new Collaborator there were a number of reviews tagged for archiving, in bulk. I now have a review that i need to retrieve. i accessed the Archiving folder on our server in an attempt to find and retrieve a review. The archive folder structure has a bunch other folder all titled like: a1, a2,a3, ff, f1.... In those folders are files titled "367s420d9f....." 1) how do i find out which file is the review i need to recover? 2) how do i open that file/unwrap it in Collaborator? Thanks!!858Views0likes1Comment