Re: persistent sign on for Zend Server

[Jim Oberholtzer <midrangel@xxxxxxxxxx>]

Very cool, I had not seen that.  Thanks for the link.....

Jim Oberholtzer
CEO/Chief Technical Architect
Agile Technology Architects, LLC


On 3/3/2011 1:36 PM, Kevin Schroeder wrote:
> Enrico Zimuel took what I wrote and made it better
>
> http://www.zimuel.it/blog/2011/02/encrypt-php-session-data/
>
>
> Kevin Schroeder
> Technology Evangelist
> Zend Technologies, Ltd.
> www.zend.com
> www.twitter.com/kpschrade
> www.eschrade.com
>
>
>
>
>
>
>
>
>
> -----Original Message-----
> From:web400-bounces@xxxxxxxxxxxx  [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf OfBMay@xxxxxxxxx
> Sent: Thursday, March 03, 2011 1:27 PM
> To: Web Enabling the AS400 / iSeries
> Subject: Re: [WEB400] persistent sign on for Zend Server
>
> Actually Larry, $_SESSION data is stored on the server.  $_COOKIE data is
> stored on the end user's computer.  a $_SESSION variable is going to be
> your best bet for doing this.  If you are still paranoid about the user
> profile and password being stored temporarily out in your IFS, you could
> always encrypt the data before storing it and then decrypt the data when
> retrieving it.
>
> In fact, search the archives, I believe Kevin Schroeder posted an example
> of doing just this kind of encryption of $_SESSION variables a while back.
>
> Brian May
> Project Lead
> Management Information Systems
> Garan, Incorporated
> Starkville, Mississippi
>
>
>
> Larry Kleinman<larry@xxxxxxxxxxxxxxxxx>
> Sent by:web400-bounces@xxxxxxxxxxxx
> 03/03/2011 01:17 PM
> Please respond to
> Web Enabling the AS400 / iSeries<web400@xxxxxxxxxxxx>
>
>
> To
> web400@xxxxxxxxxxxx
> cc
>
> Subject
> [WEB400] persistent sign on for Zend Server
>
>
>
>
>
>
> Using Zend Server, I would like to present a sign-on screen where the user
>
> enters a user ID and password to be used as the parms of the i5_connect
> function.  This is not hard, but I want to present that screen only once,
> and use that info as the user moves from screen to screen, all of which
> will require a 15_connection.  I know that I can store the user and
> password entered as $_SESSION variables, but I don;t like the idea of the
> password being written to some place on the PC hard drive.  (That's how
> $_SESSION works, right?).  Any suggestions on how to deal with this.
>
> Larry Kleinman
> Kleinman Associates, Inc.
> 212-949-6469
> 203-255-4100