Bug #1928

Document authentication workflow

Added by Vangelis Koukis over 12 years ago. Updated over 11 years ago.

Status:Closed Start date:01/09/2012
Priority:High Due date:
Assignee:- % Done:

0%

Category:Astakos Spent time: -
Target version:-

Description

Please write a short description detailing the entire authentication process, from the moment an anauthenticated client connects to a service backed by astakos, to the moment the client is authenticated and has an API token.

There are at least two distinct use cases:
a) protection of web-based services
b) protection of API calls: get an API token, use it to authenticate against an astakos-backed API

Please document the entire workflow: clients, servers, cookies, tokens, for each of the above two use cases, and any other cases you can identify.

This is a prerequisite for Alpha2 deployment.

Associated revisions

Revision 462c63e8
Added by Sofia Papagiannaki over 12 years ago

more documentation

Refs: #1928

Revision 462c63e8
Added by Sofia Papagiannaki over 12 years ago

more documentation

Refs: #1928

Revision ebb3c3bb
Added by Sofia Papagiannaki over 12 years ago

commit documentation images

Refs: #1928

Revision ebb3c3bb
Added by Sofia Papagiannaki over 12 years ago

commit documentation images

Refs: #1928

History

#1 Updated by Antony Chazapis over 12 years ago

  • Target version set to 0.2.0

#2 Updated by Antony Chazapis over 12 years ago

  • Status changed from Assigned to Resolved
  • Target version changed from 0.2.0 to 0.1.0

#3 Updated by Antony Chazapis over 12 years ago

  • Status changed from Resolved to Closed

#4 Updated by Vangelis Koukis over 11 years ago

  • Project changed from astakos to Synnefo
  • Target version deleted (0.1.0)

#5 Updated by Vangelis Koukis over 11 years ago

  • Category set to Astakos

Also available in: Atom PDF