Collaborator code review can help test developers and managers, to produce high-quality code. Teams can use it in a transparent, peer code review common framework, edit user samples and test plan.
This article focuses on what is the single sign-on? Collaborator of several single sign-on authentication method, and now look at it ~
Single sign-on (SSO) is a user authentication process, allowing the user to enter a name and password to access multiple applications. The process for the user to grant them permission to obtain all applications for authentication, and eliminates further prompts when you switch applications during a particular session. In other words, on a central server SSO enter a login name and password, the user will be automatically logged by other applications, for example, issue tracker, source code control system, code review system.
Note: only supports single sign-on authentication Collaborator Enterprise in. However, it will vary between Collaborator version.
Typically, single sign-on solution consists of several components - a SSO server and some of the SSO client. SSO authentication server is performing component, publication and validation of tokens. SSO client is integrated with a variety of software platforms and applications intermediate component for communicating through some SSO authentication protocol with the server. Most SSO solution also provides a single logout function - that is, they allow users to simultaneously log off from the application and the SSO server.
The authentication process includes the following steps:
1, Collaborator user tries to access the server.
2, Collaborator recognizes that the user is not logged, and redirects them to the SSO server.
3, SSO server to authenticate users, add some security assertions parameters, and then redirected back Collaborator server.
4, assert parameters Collaborator detect security and user login.
5, if the user is not found with the specified credentials, Collaborator will create a new user.
Logoff process includes the following steps:
1, a user attempts to log off from Collaborator server.
2, Collaborator logout request to the SSO server.
3, SSO server to a user logs off, the server sends a response back to the Collaborator.
4, Collaborator the user logs off.
Collaborator in the single sign-realization
Currently, Collaborator Web client support single sign-on authentication. It does not support desktop client (GUI client, command line client) and IDE plugins (Visual Studio extension, Eclipse plug-in) single sign-on authentication.
There are several ways you can enable single sign-on authentication:
By SAML protocol - If your SSO provider supports Security Assertion Markup Language (SAML) standard, you can configure SSO server and Collaborator server to use SAML protocol for authentication. For details, please read the configuration via SAML single sign-on (please pay attention to follow the tutorial content ~).
By Crowd OpenID protocol - If you are using Atlassian Crowd server, you can configure the server to use it and Collaborator OpenID protocol for authentication. For details, please read through the configuration Crowd OpenID single sign-on (please pay attention to follow the tutorial content ~).
By Java servlet - If your SSO SSO vendor customer-side applications in the form of Java servlet, you can install it into Collaborator server, and configure it to redirect Collaborator user to the SSO server for authentication. Read detailed instructions for configuring single sign-on Java Servlet (please pay attention to follow the tutorial content ~) through.