Apple

Thanks Chuck and Amedeo for the response.

We are about to liberate an application that would be open to the mass market. All application we have developed so far are enterprise oriented and are used on intranets.

We want that the main page of our site be a landing page that allows the user to start the process of subscription or login on the app.

We think that if we separate the site's main page from the application is the best option but I will appreciate your point of view.

On 06/11/2013, at 16:12, Chuck Hill <email@hidden> wrote:

Very briefly, you need to:

make the form submit to a direct action
get the form values manually from the request
Return the real first page if authentication succeeds
Return the login page if not. You will need to initialize with an error message if authentication failed

Chuck

--

Chuck Hill

Executive Managing Partner, VP Development and Technical Services

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.

http://www.global-village.net/gvc/practical_webobjects

Global Village Consulting ranks 13th in 2012 in BIV's Top 100 Fastest Growing Companies in B.C!

Global Village Consulting ranks 44th in 25th annual PROFIT 500 ranking of Canada’s Fastest-Growing Companies by PROFIT Magazine!

On 2013-11-06 3:57 PM, "Miguel Torres" wrote:

Hi list,

I am sure that I already have read about this some where but I can't find it.

We want to separate the login page from our application, I mean we want to create a session only if the user is authenticated.

We have been developing WebObjects apps for a long time but the login page is always the Main component, so when we open that component, a session is created even before the user tried to login.

Any hint will be very welcome.

Best Regards.

_______________________________

Ing. Miguel Angel Torres Avila

References:
	>Re: Application Login Page (From: Chuck Hill <email@hidden>)