Humanity and identity

To begin with, remenber that JCAPTCHA deals with humanity, not identity.
Humanity is a brand new notion, since only identity assertion is taken into account by common security systems.

Identity

Identity of an actor is specified by a persistant identifier, known by both the target system and the actor.
Saying of an actor that it is identified means that :

Exemple of identifiers and associated identity assertion provider :

Most of current on line systems already deals with identity.

Humanity

Humanity of an actor is not curently technologicaly specified, and there is no common way to handle it.
Saying that an actor is human means that

Those capabilities could be classified into two main categories

Most automated humanity assertion system check both capabilities.

Exemple of human capabilities and associated humanity assertion provider :

Use cases using JCAPTCHA, a humanity assertion provider

Once you have a humanity assertion mecanism, also known as weak authentication mecanism, one may use it to restrict access to services, this is the authorization.

Restricting read

Access allowed only to human

This is a standard way to protect online services that shall not be read by machine, for commercial or legal reasons.

Access allowed only to human under certain conditions

This is a weaker protection than the mentioned above : the system check that an actor is human only if after it has done specific actions.
Exemple : the system check humanity of a user only if it ask the same page more than 2 times.
This kind of use of JCAPTCHA is done to protect system against proxy machines (that re-sell a service).

Restricting write

This is the most common use case, implemented for exemple by all major free mail provider.

They use a captcha (type gimpy)to prevent massive machine registration.

Protecting user/password is also a common use case : protecting a login form with a captcha limits risks of a dictionnary attack.