Convenience and Security: Single Sign-on in codeBeamer

January 06, 2015

SSO_single_sign_on-336x336 Convenience and Security: Single Sign-on in codeBeamer alm Single sign-on (SSO) is a way to control access to multiple independent pieces of software. Basically, SSO lets you use separate tools that require user authorization (logging in with a username and password) without having to sign in to each of them: SSO takes care of the user authorization process, so you only have to log in once.

From version 7.5 on, you can use SSO (using LDAP) to integrate codeBeamer with other tools via REST API. Regardless of what (and how many) other tools your team is using, their authorization can be managed with minimal effort, saving them time and enhancing security.

Benefits of SSO

SSO is a convenient solution that, among other benefits, means a major improvement in terms of user experience. Since most large enterprises have password policies in place requiring users to change their passwords every few months, keeping track of password can be a hassle. Even with easy to remember passwords, having to log in several times can feel like a waste of valuable time. With SSO, logging users in is a seamless process that happens in the background automatically.

In addition to being highly convenient, single sign-on also results in increased security. With SSO, there is no need for a login interface, so your account is safe even if your password gets into the wrong hands.

Not only is codeBeamer a flexible tool that can be fully customized and configured to suit the needs of your organization, it is also easy to integrate in your preexisting workflow. Through REST API, codeBeamer’s functionality can be extended with any number of tools, and version 7.5 can also be configured to handle SSO. What’s more, single sign-on can also be used for applications your team is developing to improve their workflows.

Below, you’ll find an example of a REST API application based on .NET using SSO that can be used to fetch all unresolved issues assigned to a certain user.

Usage:
     >CodeBeamerUnresolvedIssues.exe -e [enpoint] -u [username] -p [password] -a [user account] -t [type] -f [file name]
        -c [converter] -n [encoding] -o -d

     -u [Username]: login user account name, default is current Windows user
     -p [Password]: login user password, if no value specified then Windows session authentication is used
     -e [Endpoint]: the codeBeamer endpoint server address (eg. https://codebeamer.com/cb)
     -a [user Account]: (optional) List the specified user's work items, by default the login user's work items are listed
     -t [Type]: (optional) Result file format. Possible values: tsv, csv, json, xml. Default: tsv
     -f [File name]: (optional) Generate the result into the specified file
     -c [Converter]: (optional)  Use special item converter (ext is implemented for now)
     -n [eNcoding]: (optional)  Output encoding (the list of usable encoding could be found in msdn,
         eg.:http://msdn.microsoft.com/en-us/library/system.text.encoding(v=vs.110).aspx )
     -o [Only directly assigned]: (optional) Show only the directly related work items to the user (not related via the user's role
     -d [Debug]: (optional) debug mode on

     Example 1:
     CodeBeamerUnresolvedIssues.exe -e https://codebeamer.com/cb -u cbprojectadmin -p cbpass -a cbdeveloper -t json -f result.json -c ext -n windows-1250 -o -d

     This will fetch unresolved issues which directly assigned (-o) to user "cbdeveloper" (-a) using codeBeamer REST API. The request authenticate with "cbprojectadmin",
     "cbpass" pair (-u,-p), the type will be JSON (-t), and the result will be generated into (-f) a file called "result.json",
     and an extended item converted will be used (-c). The result encoding will be windows-1250. Extra information about the execution will be printed (-d).

     Example 2:
     CodeBeamerUnresolvedIssues.exe -e https://codebeamer.com/cb -u cbprojectadmin -p cbpass

     This will fetch all unresolved issues for user "cbprojectadmin" (-a not specified),
     and it will print out the result in tsv format (-t not specified, tsv is the default) to console output (-f not specified, default is the console)
     in UTF8 encoding (-n not specified, UTF8 is the default output encoding)

Fore more examples on using REST API with SSO, please see the relevant section in our Knowledge Base: Example Rest API client based on .NET

codeBeamer can be simply and efficiently integrated to your current workflow via REST API. When configuring codeBeamer with SSO (using LDAP), the integration is convenient and secure as user authorization is automatically taken care of in the background.

 

facebook Convenience and Security: Single Sign-on in codeBeamer alm twitter Convenience and Security: Single Sign-on in codeBeamer alm google Convenience and Security: Single Sign-on in codeBeamer alm linkedin Convenience and Security: Single Sign-on in codeBeamer alm

Related Brochure

How to Select the ALM Solution that Best Suits Your Needs

First Name

Last Name

Email Address

Company

Phone Number

Industry

Kristof Horvath

Written by

Kristof holds a BA in Commerce and Marketing and is especially passionate about inbound and content marketing. On the Intland blog, he is covering topics related to application lifecycle management and agile methods.

Kristof Horvath has written 103 posts for Intland Software.

No comments

Leave a Reply

Your email address will not be published. Required fields are marked *