Seapine license server admin download

If the connection already exists, select it and click Edit. The Server address, Port, and Public key fingerprint fields are automatically populated. Retry the login.

TestTrack Web users. See the TestTrack Registry Utility help for information. If users cannot log in to TestTrack Web, make sure they have the security permissions to log in using web clients. Select the user's security group and click Edit.

Select General in the Command Security category. This error usually occurs for one of the following reasons:. Users need to set up a server connection if the TestTrack Server that contains the project is not available in the Server list in the login dialog box. Click Setup in the TestTrack login dialog box. Click Add in the Setup Server Connections dialog box. Click OK to add the server connection. The Projects list in the TestTrack Project Selection dialog box only contains the projects that users have access to.

If users do not have access, the TestTrack administrator must add them to the project. Log in to the project. You are here: Troubleshooting. Make sure to back up the license server database , Surround SCM Server database, and any mainline branch databases to decrease the likelihood of data loss.

Default administrative user and local admin user passwords are set on the Surround SCM Server during installation. The default administrative user Administrator lets you log in to Surround SCM for the first time to set up a mainline branch, add users and security groups, and configure server options. Change these passwords the first time you use Surround SCM to prevent unauthorized access. You can also delete this user after you set up another administrative user to replace it.

Password changes for this account in Surround SCM also affect the default login credentials for the license server admin utility and TestTrack clients. To change the local SCM admin password , update it in the general global server options. Passwords are one of the easiest ways to protect against unauthorized access.

However, many users do not set strong passwords. Effective passwords should:. Configure password requirements , such as minimum password length and required character types, in the Seapine License Server Admin Utility to force users to set strong passwords.

Note: These requirements only affect users stored on the Seapine License Server. Security groups control user access to Surround SCM actions. A user only has access to perform actions based on the enabled commands for the security group they are assigned to. Carefully consider the Surround SCM access users in different roles need and set up security groups accordingly to avoid security issues.

When creating security groups, only enable commands for the actions you want users in the group to access. This reduces the potential for users to accidentally modify data or settings they should not have access to. Security levels. Surround SCM has server, repository, and branch security. The different levels give you granular control over individual branches and repositories and let you configure more complex security scenarios when needed.

Most organizations only need to configure server security based on user roles to provide access to specific actions in all branches and repositories. You can also override security for specific repositories and branches to restrict users who can access them and the actions they can perform.

How security is applied. By default, Surround SCM security is restrictive, or pessimistic, which means no commands are enabled when you create a new security group and users can only perform actions if the corresponding command is enabled. Users can be in multiple groups. If a command is enabled in at least one group a user is in, they can perform the action.

Repository or branch security can override server security file permissions. For example, users in the Developers group can destroy files because the Destroy File command is enabled for the group. If security for the Licenses repository is modified and the Destroy File command is not enabled, users in the Developers group cannot destroy files in that repository, but they still can in other repositories because of the default server security. Repository security always overrides server security and branch security always overrides repository and server security.

Repository-level security. To manage a large number of users and projects with minimal administrative effort, consider using the following repository-level security model. Create an All Users security group to allow read-only access to all repositories. Add this security group as a baseline for all users, which you can then build on by creating other groups with more specific security settings and configuring security for specific repositories and branches.

Add all new users to this group. Configure server security for the group. Select all commands in the General category and make sure all commands in the Admin, Users, Security Groups, and Branch categories are cleared. The following screenshot shows the enabled commands for the All Users group. Optionally create a Power Users security group. To allow other high-level users, such as managers or team leads, to perform some administrative actions, create a Power Users group.

Duplicate the default Admin group , rename the new group, and clear any commands these users do not need. For example, these users may not need to edit server options or analyze, repair, or lock databases. Complete this form to request pricing, and a Seapine expert will respond to you shortly.

See this knowledgebase article. Mac OS X This one is easy to fix too. Older posts. Let's Go! Jump into Seapine today. Schedule a Demo. Start A Free Trial.