James Falek

Greenhorn
+ Follow
since Dec 17, 2003
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by James Falek

Originally posted by Marcos Maia:


This is a problem with instances of the browser ralated to java httpsessions, as far as the user already have an open window from the browser and then opens a fresh new one(without using ctrl+n) the server starts a new session for that window,(try printing the session id to check it) so the autentication does not have value for the window opened in a diferent session. To solve this the only option is targeting the window you are oppening to use the same browser instance that have the session already autenticated for the browser and not to use the other one.



Thank you very much for the feedback . There are still two issues that I don't fully understand and any help on them would be wonderful.
  • why the behavior depending upon how the initial window open (window.open vs. window.showModalDialog). When I start with window.open, the link back to to the application works fine. When I start with window.showModalDialog, I get the second LDAP authorization request.
  • why after the second login request, there are no subsequent ones - regardless of if I close the modal window and then restart it.


  • Thank you again and if you have any more ideas, I sure appreciate your insight.

    James
    [ July 20, 2004: Message edited by: James Falek ]
    17 years ago
    We have a situation where we seeing some double requests for authentication from WebLogic. Once upon application login and (sometimes) later when a link back to the web application is selected by the user.

    Here is the scenario: We are on WebLogic 7 SP5 and plan to migrate to WebLogic 8 in the next few months and use IE6 as the only browser. The web application uses basic security using a specific LDAP group which forces the user to log in and be authenticated prior to getting to the web application.

    The web application has a page which contains a javascript function that opens a modal window (uses window.showModalDialog) on another page. The modal page has a URL link (yes, having a anchor on a modal window is allowed - bizarre, but allowed (e.g., something like

    <a href="/displayFile.do?id=9444808" target="_blank">abc </a>

    When the user selects the link for the first time, the there are two different behaviors depending upon the setup:

    - if the user has no other browser windows open, the link opens a new window on top of the modal window (odd, but true) without any problems.

    - if the user had a browser window open previously, then the user is given another login prompt when they select the link on the modal page (e.g., the user initially has a browser open on cnn.com and then opens another browser from the start menu, connects to the web application logs-in, navigates to the first page, opens up the modal window and selects the link on the modal window - the user is give a second authentication prompt)

    if we change the 'window.showModalDialog' to 'window.open', we get none of this re-authentication behavior.

    We would rather not have the second WebLogic authentication and still maintain our modal windows. Does anyone have any ideas about why this behavior might be occurring? Any ideas on how to solve this and continue using modal windows?

    Thank you,

    James
    17 years ago
    We have a situation where we seeing some double requests for authentication from WebLogic. Once upon application login and (sometimes) later when a link back to the web application is selected by the user.

    Here is the scenario: We are on WebLogic 7 SP5 and plan to migrate to WebLogic 8 in the next few months and use IE6 as the only browser. The web application uses basic security using a specific LDAP group which forces the user to log in and be authenticated prior to getting to the web application.

    The web application has a page which contains a javascript function that opens a modal window (uses window.showModalDialog) on another page. The modal page has a URL link (yes, having a anchor on a modal window is allowed - bizarre, but allowed (e.g., something like

    <a href="/displayFile.do?id=9444808" target="_blank">abc </a>

    When the user selects the link for the first time, the there are two different behaviors depending upon the setup:

    - if the user has no other browser windows open, the link opens a new window on top of the modal window (odd, but true) without any problems.

    - if the user had a browser window open previously, then the user is given another login prompt when they select the link on the modal page (e.g., the user initially has a browser open on cnn.com and then opens another browser from the start menu, connects to the web application logs-in, navigates to the first page, opens up the modal window and selects the link on the modal window - the user is give a second authentication prompt)

    if we change the 'window.showModalDialog' to 'window.open', we get none of this re-authentication behavior.

    We would rather not have the second WebLogic authentication and still maintain our modal windows. Does anyone have any ideas about why this behavior might be occurring? Any ideas on how to solve this and continue using modal windows?

    Thank you,

    James
    17 years ago
    Hi,

    I am on a team implementing a multiple-config struts application. When a user comes in the first time, they are forced to login and we setup their initial context. As they go through the application, not only does their context can change, but the information for which they have access as well as which capabilities for that information. Our urls are fairly clean, typically with the form of http://abc.com/feature1/action1.do . We have one case where we have put attribute information on the url.

    However, our users want to be able to bookmark a page and we are trying to come up with ways to implement this. We could redo all of the struts-configs and put more information on the url. But that seems to defeat much of the work to make the interface clean and maybe even "de-leverages" the multiple struts configs.

    Regardless of the issues, we are lookinf for ideas - glimmers of thoughts - that might lead us a good design and implementation path.

    Thank you ahead of time

    James
    18 years ago
    Thank you for the insight - unfortunate as it might be ;-(
    Thanks again,
    James
    18 years ago
    Is it possible to use the JSTL expressons along with Struts tags? On a JSP page, I have a bean defined which contains a map of lists (with a Dynaform). I am able to successfully access the bean for non-struts items like the following:
    <select name='sites' id='sites' >
    <c:forEach items='${myBean.lists.sites}' var='siteName'>
    <option value="<c:out value='${siteName}'/>"> <c:out value="${siteName}"/> </option>
    </c:forEach>
    </select>

    However, when I try the following, I get an error:
    <html:select property='sites'>
    <html:options collection="${myBean.lists.sites}"/>
    </html:select>
    with the error stating:
    Cannot find bean under name org.apache.struts.taglib.html.BEAN

    Since the non-struts select works, I am wondering if something else is required to get Struts working with the JSTL expression language. I have also tried changing the options to the following:
    <html:options collection="<c:out value='${myBean.lists.sites}'/>"/>
    Thank you.
    18 years ago