Version :

Release Date : 26/12/2014

Download Link :  CelloSaaS4.5


1. Microsoft .NET Framework or higher

2. Visual Studio 2012 or higher

3. MS SQL Server 2008 or MS SQL Server 2012

4. ASP.NET MVC 5.2

5. Windows 7 or Windows 8 for Development machine

6. Windows Server 2008 / R2 or Windows Server 2012 / 2012 R2 for Production Deployment

Installation Guide

CelloSaaS is shipped with the following variants, 

1) Precreated Solution / Portal

You can use the pre-packaged solution which contains the Authorization Server and the Web Client application. This solution has the configuration files updated with the corresponding URI's that can be readily run after changing the SQL.config file.

This solution contains the following files


Contoso.WebApp [The client application]

Contoso.AuthServer [Authorization Server]

2) VSIX Installer

1. Install "CelloSaaSPackage.vsix"

2. Open VS2012, File->New Project 

3. Choose Visual C#-> CelloWeb project template

4. Choose Visual C#-> CelloAuthServer project template

Common Steps

Create a database (e.g. "CelloSaaSDb") and execute DbScripts\SQL Server Scripts\CelloSaaSDb.sql and change the

Connection String in following files.

  1. Contoso.AuthServer (Authorization Server)\Config\Sql.Config
  2. Contoso.WebApp (Client Application\Sql.Config

The following configuration to be done


authServerConfig.json [Contoso.AuthServer (Authorization Server)\Config\ authServerConfig.json]

URI Settings, the URLs in the given configuration settings are to be replaced with your deployment URLs 


"Audience": "http://localhost:37202/",
"AuthIssuer": "http://localhost:37202/",
"ClientApplicationUri": "http://localhost:60922/", 



Audience - AuthServer  hosted address (E.g : or http://localhost:1200)

AuthIssuer - AuthServer   hosted address (E.g : or http://localhost:1200)

ClientApplicationUri - Web Client hosted address (E.g or http://localhost:1400)

2.Web Client

AppSettings.Config [Contoso.WebApp (Client Application)\Config\AppSettings.Config]

URI Settings, the URLs in the given configuration settings are to be replaced with your deployment URLs 


 <!--Authorization Server Settings-->
  <add key="AuthServerUri" value="http://localhost:37202/"/>
  <add key="AuthIssuer" value="http://localhost:37202/"/>

 AuthServerUri - AuthServer  hosted address(eg: or http://localhost:1200)

 AuthIssuer - AuthServer  hosted address(eg: or http://localhost:1200)  


Run the Authorization Server followed by the web client.


In order to consume the Social Logins, the developer accounts have to be set-up for the following providers. The client identifier and the secrets to be registered in the given links and then the corresponding re-direct URI registrations to be made in the "authServerConfig.json" file.

Google []

Twitter []

Facebook []

Product Admin login credentials:

Company Code: company

User name:

Password: company#123

New Features

S.No Title Description

Authorization Server

The Cello Authorization Server enables the decoupling of the identity and authentication from the application and thus provides an option for plugging-in any custom authentication that supports the OAuth 2.0 or the OpenId Connect 1.0 Protocol Specification 
 Any application can consume identity and authorization as a service that can be used to gain access to the secured resources on behalf of the user

Database Analytics

This is an analytics tool that helps the ISV admin to get an insight into the database performance and the level of usage of the database at the tenant level also. 

Cello REST Services

The basic multi-tenant services are exposed via REST services in Cello. This enables a language independent interoperability to consuming Cello Services.

Billing Enhancements

The tax component addition for the tenant at the global and at the tenant level can be applied

Minimal Effort Multi-Tenancy

This module is to enable the ISV to port from single tenant model to multi-tenant model from the GUI. This module generates the scripts that can manage the database level of multi-tenancy with very low effort and automated tenant isolation in addition to partition support.


Click here for assistance in migrating from Techcello ver. to Techcello ver.