Release Notes
Release notes are provided to support the installation of the latest product version. In the notes you will find information about any new functionality that we've added, what fixes are now in place, and if there are existing issues of which you should be aware.
Release 1.0.0.2 Build:136502
The first release of Access Control Plus is now available. Below are noted the remaining issues that you should be aware of before you install or deploy.
- Addressed an issue with the Node Repair tool which did not stop an external nodes from being selected for use as the "helper". The use of non-local nodes as helpers will be supported in a future release but currently some steps in the repair are not replicated. ACP-1289, ACP-1254
- We've put in a temporary change to the Repair Tool that prevents a non-local node from being selected as helper. ACP-1294
Known Limitations
- The "Deny" setting (blocking reads or write access) is currently not available for the Git references in Access Control Plus. It will become available if we're able to implement finer grained read permissions on Git repositories. ACP-912
- Currently a "Read" rule (R+) is required at the Repository level in order for any rules that applying to Git References to work. IF there's no Read rule set then access to the reference will be denied and no warning will be given. ACP-911
- Access to Access Control Plus's admin console will be blocked by Microsoft Internet Explorer 11 when runing in enterprise mode. To unblock access, add the admin console's URL Internet Explorer's the site list manager to be able to access the admin console.ACP-790
See our article on how to Unblock Access Control Plus when using IE11 in Enterprise Mode
- When using Batch updates and switched on, the Pending mode's database needs to initialized by running a batch update. Otherwise the Current mode database will not actually reflect the current state. ACP-732
- Team leader (with full permissions) cannot promote sub-team member to team leader as he cannot grant them any permissions ACP-993
- Currently it is not possible to remove LDAP settings that have been applied to teams. This issue will be addressed as a matter of urgency. ACP-941
- We strongly recommend that you guard against the adding of LDAP-based accounts that use the same account name. Currently there's no guard against having two accounts with the same name - as accounts can be distributed accross any number of authorities. In the event that you attempt to add two accounts that use the same account name, their addition will fail and an error message will appear in the logs that warns you of an "Incorrect result size: expected 1, actual 2". ACP-917
- Repositories (w/o templates) currently can't be deleted until they are assigned a template. ACP-1027
- If you have two repositories with the same name (also of the same SCM type) then currently a rule lookup that will display them will currently only show one of the repositories (chosen randomly). We'll address this issue in a future release. ACP-1024
- There is currently a small chance that the induction of a node will fail - the induction would appear to freeze with a "Triggering induction" message, with a corresponding pending induction task. If this happens it won't be possible to un-induct the failed node. However, it is possible to induct new nodes, and it is also possible to connect to MultiSite using those nodes. Any changes to Access Control settings (e.g. templates, resources, teams, users, rules etc.) are replicated to all nodes except the broken one. Replication of Apache password and Authz files also work as expected. ACP-1114
- Currently the browser-based admin console requires that you include the /ui/ directory in its URL (i.e. http://10.0.0.5:8082/ui/). In a future release we'll ensure that any request on the application port will redirect to the admin console.ACP-1044
Release 1.0 Build 1362
The first release of Access Control Plus is now available. Below are noted the remaining issues that you should be aware of before you install or deploy.