Repository Access Management - techtalk/SpecLog-Resources GitHub Wiki
Access to shared repositories can be managed individually for each user registered on the server.
Access permissions for a repository depend on the repository role configured for the user:
| Repository role | Permissions |
|---|---|
| regular | Access to the repository (read/write data) See the repository in the list of server repositories |
| admin | Access to the repository (list, read/write data) See the repository in the list of server repositories Rename or delete the repository on the server Manage repository permissions and roles for the repository Start/stop plugins for the repository (from SpecLog client only) |
| none, the user has server admin role | Rename and delete the repository on the server See the repository in the list of server repositories Manage repository permissions and roles Start/stop and configure plugins for the repository (from SpecLog client only) |
| none, the user has server regular role | No access, and the repository is not visible to the user when browsing the server |
Note: Users publishing or creating a repository on the server are automatically granted the admin role for that repository.
You can manage repository permissions from both the SpecLog client and the SpecLog.AccessManager command line tool.
Select Manage repositories from the main menu to connect to the desired server and manage repository permissions:
You can also configure the server plugins from this dialog for repositories you have access to.
You can use the SpecLog.AccessManager command line tool to list, grant or revoke repository access permissions.
In order to manage permissions, you need to provide a user token file that has sufficient permissions for the server and repository. By default, a file with the name admin.sltoken is expected in the startup directory; you can explicitly specify another token file path using the /adminToken: parameter.
Like the SpecLog client, the command line tool requires network access to the SpecLog server service, and the network name of the user token file used has to match the SpeclogServerUrl value configured in the SpecLog.AccessManager.exe.config file.
For more information on specific commands, enter:
>SpecLog.AccessManager.exe help