I have an authorization scheme where by the user is presented with a sign in
page. After signing in, a check is made to see if they need to change their
password. If so, they are redirected to a change password page. After that
they should be redirected back to their intended page.
I don't think that is possible but why can't you do the following:
user enters username and password on sign in page.
form successfully authenticates user.
try to continueToOriginalDestination or if there is none, set the
responsepage to a homepage or something
do the password change check
if
I have an authorization scheme where by the user is presented with a
sign in page. After signing in, a check is made to see if they need to
change their password. If so, they are redirected to a change password
page. After that they should be redirected back to their intended page.
However,
I am using 1.3 and the RestartResponseAtInterceptPageException generates an
absolute versus relative URL and is not working with external web cache
solution. Is this a bug?
Mike
--
View this message in context:
mchack wrote:
I am using 1.3 and the RestartResponseAtInterceptPageException generates an
absolute versus relative URL and is not working with external web cache
solution. Is this a bug?
If you do a 302 redirect using the servlet-api with a relative URL, the
servlet container will rewrite it
Unless I'm missing something, not without some major cut pasting (or
a custom version or Wicket). The actual onSubmit() is down in
SignInForm, which is in SignInPanel, which is in SignInPage. Even if
it wasn't final, (which it is,) then there doesn't seem to be a way of
getting to it to
Ah. I'm not sure how many people actually use SignInPanel. Indeed,
that component doesn't look particularly flexible. I guess what you're
looking for is something like:
Index:
/Users/eelcohillenius/Documents/workspace/wicket-auth-roles/src/main/java/wicket/authentication/panel/SignInPanel.java
Hi,
The login-example uses RestartResponseAtInterceptPageException to forward
a user to the login page when he's not authorized.
What is the difference with throwing an RestartResponseAtInterceptPageException
instead of a RestartResponseException exception? The latter appears to give the
same
The difference is that RestartResponseAtInterceptPageException records
the current request first, which then later - after logging in - could
be redirected to again.
if (!continueToOriginalDestination()) {
setResponsePage(getApplication().getHomePage());
}
Eelco
On
On a related note, can anyone suggest a good way of adding a way of
changing the 'destination' page as part of the logging in?
The scenario is that after authenticating the user, I may to redirect
them to a 'ChangePassword' page. Is there a better answer than a
RestartResponseException in my
On 09/10/06, Gwyn Evans [EMAIL PROTECTED] wrote:
On a related note, can anyone suggest a good way of adding a way of
changing the 'destination' page as part of the logging in?
The scenario is that after authenticating the user, I may to redirect
them to a 'ChangePassword' page. Is there a
So before the user is logs in?so in the end you have 2 login pages?Or after the users logs in, so 2 different directions when the login succeeds?johanOn 10/9/06,
Gwyn Evans [EMAIL PROTECTED] wrote:
On a related note, can anyone suggest a good way of adding a way ofchanging the 'destination' page
After the login's how I was hoping to go... Currently checking the
(session) stored user details in the BasePage.
/Gwyn
On 09/10/06, Johan Compagner [EMAIL PROTECTED] wrote:
So before the user is logs in?
so in the end you have 2 login pages?
Or after the users logs in, so 2 different
if it is after login. Can't you handle it then in the login.onSubmit code?johan\On 10/9/06, Gwyn Evans
[EMAIL PROTECTED] wrote:After the login's how I was hoping to go...Currently checking the
(session) stored user details in the BasePage./GwynOn 09/10/06, Johan Compagner [EMAIL PROTECTED] wrote:
Hi,
I have a link that redirects to a page where should be a link back to the original page. I tried to use RestartResponseAtInterceptPageException to accomplish this.
OriginalPage:
public OriginalPage() {
...
add(new Link(link) {
public void onClick() {
throw new
What is the original page?Really the page with the link on it?So when you click a link on it your wnat to redirect and return to the page with the link on it?Curious what the case would be for that.i think you just need to use this class:
public RestartResponseException(Page page)and then youre
I'll explain the use case:
There is a general properties page that is called from several other pages. User uses this just to see the properties of the object. And when the user has seen enough he wants to click the back button to continue what ever he was doing.
OK, the properties page could
why not pass in a page reference into the properties page. that way you can just setResponsePage(backPage) in your back link handler.-IgorOn 2/9/06,
Arto Arffman [EMAIL PROTECTED] wrote:
I'll explain the use case:
There is a general properties page that is called from several other pages. User
Yes, that is one way to solve this. Apparently I misunderstood the purpose of RestartResponseAtInterceptPageException. I guess it is meant for intercepting on situations like authorization (no other use case comes into my mind).
Thanks for your help.
/arto
2006/2/10, Igor Vaynberg [EMAIL
19 matches
Mail list logo
