[
http://jira.amdatu.org/jira/browse/AMDATUAUTH-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivo Ladage - van Doorn moved AMDATU-202 to AMDATUAUTH-33:
---------------------------------------------------------
Project: Amdatu Auth (was: Amdatu)
Key: AMDATUAUTH-33 (was: AMDATU-202)
Affects Version/s: 0.1.0
(was: 0.1.0)
Component/s: (was: Amdatu Auth)
Fix Version/s: 0.1.0
(was: 0.1.0)
> Associate authorize token step of oAuth dance with Amdatu login service or
> even pluggable login service
> -------------------------------------------------------------------------------------------------------
>
> Key: AMDATUAUTH-33
> URL: http://jira.amdatu.org/jira/browse/AMDATUAUTH-33
> Project: Amdatu Auth
> Issue Type: Task
> Affects Versions: 0.1.0
> Reporter: Ivo Ladage - van Doorn
> Assignee: Bram de Kruijff
> Fix For: 0.1.0
>
>
> The authorization token part of the process is currently a micky mouse
> example. By simply posting a form holding the userid, a request token can be
> authorized for that user id. This needs to be connected to the Amdatu login
> service, or even to a pluggable login service.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
