Configuration for a multi-server environment
For environments that are larger and need some server redundancy, it would be nice to have a multi-server configuration available. The servers would be behind a load balancer of some sort and traffic would be divided between the two or more servers hosting the Collaborator application.5.8KViews3likes1CommentMigrating 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, ~Chris2KViews0likes1CommentMore Granular access controls for Subscription settings
The Subscription settings currently have only two parts, one specifying who can change them when someone is automatically added, and one specifying who can modify subscriptions. The Subscription settings are configured on each user account as to what they want to be automatically subscribed to. The setting related to who can modify those is either "Administrator", meaning only an administrator can modify any subscription settings for what users are subscribed to, or "User" meaning all users can modify their own subscription settings. Most of our users are not trusted enough to modify their own subscription settings, so we're currently using "Administrator" for the restriction, but we have a collection of Senior Developers and Project Leads that need/want to be subscribed to a number of different things and are trusted enough to modify their own subscription settings. The only solution is to currently make those trusted users Administrators, or to have one of the existing Administrators modify the user's settings whenever they need/want to change their subscriptions.1.6KViews0likes0CommentsSSO 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.3KViews0likes1CommentAWS Code Commit Support
Howdy, Please add Code Collaborator support for AWS Code Commit repository integrations to the web client. Example of this current functionality can be found here: https://support.smartbear.com/collaborator/docs/source-control/git.html https://support.smartbear.com/collaborator/docs/source-control/repo-hosting/index.html In the same way that Github, Bitbucket, and Azure can easily be integrated to the Collaborator, I would like for this process to also function with AWS Code Commit Repos. I may currently use Code Collab and AWS Code Commit via the client gui and local changes, but I would also like to have direct repo integration like the hosted repos do. Thanks.1.3KViews1like2CommentsAllow anyone to re-open a closed review by clicking a link, NOT by adding a comment
Users are complaining about this setting: Allow Reopening Completed Reviews Once a review has completed, should participants be allowed to re-open the review just by making an additional comment? If not allowed, an administrator is still able to re-open a review by clicking a link. They want to be able to comment on a Closed review without Re-opening it, but also be able to Re-open reviews without an Administrator. One way would be to make the re-open link mentioned above available to all - maybe add a separate setting to enable that...1.2KViews1like0Comments