You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2010/09/20 11:33:32 UTC

[jira] Resolved: (SLING-1785) Support optional request parameters after login redirect

     [ https://issues.apache.org/jira/browse/SLING-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger resolved SLING-1785.
--------------------------------------

    Resolution: Fixed

In Rev. 998847 adapted the OpenID authentication handler to use the new redirect support method to redirect the client to the initial (Sling) OpenID identifier entry form. For the redirect cycle through the OpenID provider a similar mechanism must be implemented to ensure the request parameters are saved across the OpenID provider redirect cycle (getEncodedReturnToResource and getDecodedReturnToResource methods).

This completes this enhancement

> Support optional request parameters after login redirect
> --------------------------------------------------------
>
>                 Key: SLING-1785
>                 URL: https://issues.apache.org/jira/browse/SLING-1785
>             Project: Sling
>          Issue Type: Improvement
>          Components: Authentication
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: OpenID Authentication 1.0.2, Form Based Authentication 1.0.2, Auth Selector 1.0.2, Auth Core 1.0.4
>
>
> Upon redirect to the login form, any request parameters provided as part of the request URI (e.g. thepage.html?param=x) should be conserved during the form redirect cycle. Currently such parameters are lost.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.