Re: Regarding SSO across admin console
Hi Joseph, Thanks for the response. I figured it out. I was not doing something correctly as mentioned in the other mail I sent. I was developing an EJB Server portlet for the console and was facing an error there. Will be attaching a patch shortly. Regards Manu On Thu, Feb 28, 2008 at 2:29 AM, Joseph Leong <[EMAIL PROTECTED]> wrote: > Hi Manu, > > As Kevan mentioned - I ran into a similar issue as well while working on the > plugin installer in console. But I can't say it better than Joe Bohn > (above), the issue rooted from the JSessionID getting corrupted. So the > first suggestion would be to verify whether the JSessionID is getting > corrupted or deleted. Let us know what ya find and hopefully we can step > through this. > > Which portlet is this for? > > -Joseph Leong > > > On Wed, Feb 27, 2008 at 12:19 PM, Joe Bohn <[EMAIL PROTECTED]> wrote: > > > > > > > > Manu George wrote: > > > Hi, > > >I added a new portlet to the admin console via the newHi > > > > > > > > > pluggable mechanism. However when I click on the link to that portlet > > > I am always asked to authenticate even though I have authenticated on > > > the login page of the admin console. How can I configure my portlet to > > > also be part of the single sign on across the admin console. > > > > > > Regards > > > Manu > > > > > > > > > > > > > Hi Manu, > > > > I don't know the answer but here are some things you can investigate: > > > > 1) I know that we had issues with this and the pluggable console > > earlier with Jetty. I thought those issues were resolved but if you are > > using Jetty you might want to give Tomcat a try. > > > > 2) The problem you describe typically happens with the portlet session > > gets corrupted/reset or when the JSessionID cookie gets > > corrupted/deleted. You might want to check if you are doing anything > > special that might affect the session. > > > > Finally, the doc that Kevan referenced includes a sample. You might > > want to try that sample first and then begin adding in your specifics > > until the problem surfaces. > > > > Joe Bohn > > > > > >
Re: Regarding SSO across admin console
Thanks Joe Kevan for the hints. I figured it out. I was using the ContextForwardServlet and the ForwardDispatchFilter for DWR. But I was still referring to my context in the JSP to access the DWR scripts instead of console :(. This was causing the repeated authentication requests. Another problem I faced was with the TreeV3 from dojo. The alignment for this is broken in IE7 and so in all the portlets in console using it. There is also an incompatibility between DWR and Dojo 0.9 tree Data Stores. So my only choice was to use dojo.widget.Tree. I will update the wiki article with this information and maybe modify the sample to use DWR. Regards Manu On Wed, Feb 27, 2008 at 10:49 PM, Joe Bohn <[EMAIL PROTECTED]> wrote: > > Manu George wrote: > > Hi, > >I added a new portlet to the admin console via the new > > pluggable mechanism. However when I click on the link to that portlet > > I am always asked to authenticate even though I have authenticated on > > the login page of the admin console. How can I configure my portlet to > > also be part of the single sign on across the admin console. > > > > Regards > > Manu > > > > Hi Manu, > > I don't know the answer but here are some things you can investigate: > > 1) I know that we had issues with this and the pluggable console > earlier with Jetty. I thought those issues were resolved but if you are > using Jetty you might want to give Tomcat a try. > > 2) The problem you describe typically happens with the portlet session > gets corrupted/reset or when the JSessionID cookie gets > corrupted/deleted. You might want to check if you are doing anything > special that might affect the session. > > Finally, the doc that Kevan referenced includes a sample. You might > want to try that sample first and then begin adding in your specifics > until the problem surfaces. > > Joe Bohn > >
Re: Regarding SSO across admin console
Hi Manu, As Kevan mentioned - I ran into a similar issue as well while working on the plugin installer in console. But I can't say it better than Joe Bohn (above), the issue rooted from the JSessionID getting corrupted. So the first suggestion would be to verify whether the JSessionID is getting corrupted or deleted. Let us know what ya find and hopefully we can step through this. Which portlet is this for? -Joseph Leong On Wed, Feb 27, 2008 at 12:19 PM, Joe Bohn <[EMAIL PROTECTED]> wrote: > Manu George wrote: > > Hi, > >I added a new portlet to the admin console via the newHi > > pluggable mechanism. However when I click on the link to that portlet > > I am always asked to authenticate even though I have authenticated on > > the login page of the admin console. How can I configure my portlet to > > also be part of the single sign on across the admin console. > > > > Regards > > Manu > > > > Hi Manu, > > I don't know the answer but here are some things you can investigate: > > 1) I know that we had issues with this and the pluggable console > earlier with Jetty. I thought those issues were resolved but if you are > using Jetty you might want to give Tomcat a try. > > 2) The problem you describe typically happens with the portlet session > gets corrupted/reset or when the JSessionID cookie gets > corrupted/deleted. You might want to check if you are doing anything > special that might affect the session. > > Finally, the doc that Kevan referenced includes a sample. You might > want to try that sample first and then begin adding in your specifics > until the problem surfaces. > > Joe Bohn > >
Re: Regarding SSO across admin console
Manu George wrote: Hi, I added a new portlet to the admin console via the new pluggable mechanism. However when I click on the link to that portlet I am always asked to authenticate even though I have authenticated on the login page of the admin console. How can I configure my portlet to also be part of the single sign on across the admin console. Regards Manu Hi Manu, I don't know the answer but here are some things you can investigate: 1) I know that we had issues with this and the pluggable console earlier with Jetty. I thought those issues were resolved but if you are using Jetty you might want to give Tomcat a try. 2) The problem you describe typically happens with the portlet session gets corrupted/reset or when the JSessionID cookie gets corrupted/deleted. You might want to check if you are doing anything special that might affect the session. Finally, the doc that Kevan referenced includes a sample. You might want to try that sample first and then begin adding in your specifics until the problem surfaces. Joe Bohn
Re: Regarding SSO across admin console
On Feb 26, 2008, at 6:59 PM, Jacek Laskowski wrote: On Tue, Feb 26, 2008 at 11:48 AM, Manu George <[EMAIL PROTECTED]> wrote: I added a new portlet to the admin console via the new pluggable mechanism. You guys seem to speak some cryptic language I don't understand lately ;-) What's the "new pluggable mechanism". Is there anything on the wiki/ in the docs? There's http://cwiki.apache.org/GMOxDOC21/extensible-administration-console.html And also this (which needs to be copied into the developer's guide -- http://cwiki.apache.org/GMOxDEV/administration-console-extension-developers-guide.html However when I click on the link to that portlet I am always asked to authenticate even though I have authenticated on the login page of the admin console. How can I configure my portlet to also be part of the single sign on across the admin console. I don't know the answer, but is there anything on the console? I think Joe Leong might be able to help Manu. Joe was submitted some console patches just prior to 2.1. --kevan
Re: Regarding SSO across admin console
On Tue, Feb 26, 2008 at 11:48 AM, Manu George <[EMAIL PROTECTED]> wrote: >I added a new portlet to the admin console via the new > pluggable mechanism. You guys seem to speak some cryptic language I don't understand lately ;-) What's the "new pluggable mechanism". Is there anything on the wiki/in the docs? > However when I click on the link to that portlet > I am always asked to authenticate even though I have authenticated on > the login page of the admin console. How can I configure my portlet to > also be part of the single sign on across the admin console. I don't know the answer, but is there anything on the console? Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
