-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

HTTP Basic authentication was added to the WebPagePortlet on 3/29/02.  The 
authentication is between the Portlet Server and the "secured" content 
provider.  The result is that the first page can be loaded using the 
configured username and password but any link from within that page will 
result in a password prompt. (HTTP 401)

I keep trying to find the time to contribute a new WebPageProxyPortlet that 
will allow you to navigate a site within the confines of the Portlet 
container, including login credentials (HTTP Basic & Digest, or Cookies).  
I have a functional version running in a production environment that needs 
to be generalized for public consumption.  Check the developer's list in a 
week or so...

DP


On Thursday 30 May 2002 04:26 am, KARTHIKEYAN�E S wrote
> hi all,
>
> I have embeded our intranet sites as webpageportlets in JetSpeed. Almost
> all the sites have to be logged in with a username and password.
> Incidentally, all the intranet sites share the same pair of Username and
> password for a particular user (ie., a user has same username and
> password for all the intranet sites) .
>
> To access those sites a jetspeed user has to type the username and
> password in all the WebPagePortlets.  To avoid this , if the Jetspeed
> user is created with same User Name and Password, Is it possible to fetch
> the UserName and Password of a Jetspeed user and pass them to
> WebPagePortlets so that sign in need not be done for each portlet. It may
> resemble more like Single Sign on but is it possible to achieve this.
>
> with thanks and regards,
> karthikeyan

- -- 
David G. Powers
PowerSource
-----BEGIN PGP SIGNATURE-----
Comment: Verify the authenticity of this message with the public key available at 
http://pssp.com/dgp_pk.asc

iD8DBQE89k5cjmjAPDT0/nERAoE2AJ4g9LdNL4gsiYrpBEfUMoUtuOjC0wCfYukX
Cyz2RjvlyoMKzthskL20mrQ=
=3Bw/
-----END PGP SIGNATURE-----

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to