«A Ticket Me» Service Presentation

February, 20111/2221 AD © SoftStructor Ltd. «A Ticket Me» Service.

http://aticket.me

A Ticket Me

Identification Service


Authorization types

There are several types of the users authorization:

⁕ Classical

⁕ OpenID

⁕ OAuth


Classical Authorization

This method allows to identify user via login name and password.

- each user should follow the registration process.- each user have to remember the login/password

Finally the user has an enormous amount of logins and passwords.

… let's remember how often do you click the 'Forgot password' link?


Classical Authorization

There are examples of the classical authorization process. It is simple way to identify the user.

Did you notice? The login name has evolved to the 'email'. The reason of it is global uniqueness of the 'email' box name over the world. It means that user wouldn't check the uniqueness of the login name at the registration.


OpenID and OAuth Authorization

There are plenty of OpenID or OAuth providers, but none of them get flexible integration (CID profiling, UserData delivery, Event propagating)


OpenID and OAuth Authorization

As you can see along with the classical authorization you are able to log in via OpenID or OAuth.

What is the difference between the OpenID and OAuth authorization types? Let's see the next slide...


OpenID and OAuth. The Difference

In this case the OAuth goes the same way. It is the reason of mixing usage (OpenID – authorization/registration, OAuth – widget integration with background authorization)

The case when the user is not authorized at the provider


OpenID and OAuth. The Difference

This slide shows the key difference. In this case the user has already authorized at the OpenID/OAuth provider.

Pay attention. In both cases the user must be registered at the OpenID/OAuth provider.


What solution would we like to offer?

Our thesis:

* We believe that the user's email is necessary and sufficient for the identification

* We believe that almost all users have email boxes

* The right to anonymity should reserve at each user

* The flexibility and the scalability of the service integration

* Simplicity for the user


The «A Ticket Me» Service Is...

The identification center:

* allows to identify the user without registration process* each user has the ability to customize his own profile for various resources* is able to have more than one email address per user

The integration center:

* each user is able to become as an agent* each agent can register a couple of his own resources* agent's resources have two way for the integrations – user's data delivery and event propagating.


How it works ? It's Easy

The user enters his e-mail and your site makes SOAP/JSON-request for the authorization key. «A Ticket Me» creates the authorization URL based on this key and send it to the user's e-mail.

The user follows back by URL that he/she has just received via e-mail.

… and nothing more!


How it works from the user's side










User Data Delivery

The user's data can be delivered for one of your sites.

What about privacy? The data set can be encrypted and the third side will be not able to read it.


Event Propagation

Unlike the user's data delivery, the event propagation is the process of the instant notification transferring to subscribers.


Security notes

⁕ The «A Ticket Me» service does not store any passwords. It is the profile storing only.

⁕ All integration interfaces use encrypted channels only

⁕ The both processes, such as the user's data delivering and the event propagating are able to use encrypted contents.


Where is the profit?

⁕ It is necessary for a user to have an e-mail only.

⁕ There is no necessity in enormous amount of logins and passwords.

⁕ Easy integration via most popular SOAP/JSON

⁕ Your services give the ability to delivery the private information between the group of the cites.


SaaS. Obvious Profit

The «A Ticket Me» service is not boxed software. It is pure SaaS (software as a service).

The main reason of growth SaaS usage is reducing the cost of ownership.

The SaaS trend confirms that:

Oct 28, 2008 http://www.gartner.com/it/page.jsp?id=783212 © Gartner, Inc

“Worldwide software-as-a-service (SaaS) revenue in the enterprise application markets is on pace to surpass $6.4 billion in 2008, a 27 percent increase from 2007 revenue of $5.1 billion, according to Gartner, Inc. The market is expected to more than double with SaaS revenue reaching $14.8 billion in 2012.”

Dec 14, 2010 http://www.gartner.com/it/page.jsp?id=1492814 © Gartner, Inc

“Worldwide software as a service (SaaS) revenue within the enterprise application software market is forecast to reach $9.2 billion in 2010, up 15.7 percent from 2009 revenue of $7.9 billion, according to Gartner, Inc. The market is projected for stronger growth in 2011 with worldwide SaaS revenue totaling $10.7 billion, a 16.2 percent increase from 2010 revenue.”


Thank You!

Date post:	29-Apr-2015
Category:	Technology
Upload:	softstructor-ltd
View:	470 times
Download:	4 times

«A Ticket Me» Service Presentation

Technology