profile image
John Kohl
Software Engineer
Posts by John Kohl
Secure DevOps | November 17, 2021
Working with VersionVault Express outside the browser
VersionVault Express’s primary UI is a browser-based application. It supports editing and saving single files, comparing files and reviewing change sets, simple cases of rebasing and delivering between streams, and more.
Secure DevOps | October 18, 2021
Introduction to VersionVault Express concepts
This article will describe how VersionVault Express manages versioned assets using the capabilities of VersionVault Unified Change Management (UCM). 
Secure DevOps | September 29, 2020
More Flexibility for VOB Element Protection
WHAT'S THE PROBLEM?     HCL VersionVault administrators often need to set up access controls on VOB elements to meet their companies' information security policy.  Operating system groups are a popular way to manage protections: users are assigned to groups, and those groups are used for element access checks.    This works nicely when groups are used for VOB element access control lists (ACLs), introduced in VersionVault 8.0.1, or for UNIX-style mode bit checks based on the VOB element's group ownership.  However, it only works as long as a single user only needs 16 or fewer groups to access all authorized elements.  VOB element ACLs can reduce the need for a user to be a member of multiple groups:  instead of having one user with multiple groups accessing elements each with a single group, you configure the ACL to protect elements to be accessible by multiple groups and each user only needs one (or a few) group(s) to access the elements.    For example, a shared component "S" would allow access to the groups representing the teams that consume that component ("A" and "B") and to the team that maintains the component ("S").  Then the developers of components A and B only need membership in the respective team-group (A or B), and the developers of the shared component only need membership  in group S.    But some administrators had extra burdens managing their group membership this way: their organization's security policy was built around separate groups for each component, with users assigned membership in the groups needed for all components their project used. ACLs could solve the problem technically but the management of ACLs to allow multiple groups per element had a higher administrative overhead than using a single group per element.    In the above example, developers for component A need membership in group...
Filters result by