[
http://jira.amdatu.org/jira/browse/AMDATU-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivo Ladage - van Doorn resolved AMDATU-202.
-------------------------------------------
Resolution: Fixed
Authorize step is replaced by Amdatu login/allow access step. If you're already
logged in the login step will be skipped.
It is pluggable in the sense that in ConfigAdmin you can define an alternative
authorize URL, pointing to a custom authorize page. Note that no matter how
this page is implemented, as a result the Authorize token servlet should be
invoked with the request token to authorize, but only after a successful Amdatu
login.
> Associate authorize token step of oAuth dance with Amdatu login service or
> even pluggable login service
> -------------------------------------------------------------------------------------------------------
>
> Key: AMDATU-202
> URL: http://jira.amdatu.org/jira/browse/AMDATU-202
> Project: Amdatu
> Issue Type: Task
> Components: Amdatu Authentication - oAuth
> Affects Versions: 0.1.0
> Reporter: Ivo Ladage - van Doorn
> Assignee: Ivo Ladage - van Doorn
> 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
