Forum Stats

  • 3,853,849 Users
  • 2,264,287 Discussions
  • 7,905,480 Comments

Discussions

SSL & Portal Configuration

LBROCKS
LBROCKS Member Posts: 34
edited Oct 9, 2008 10:34AM in WebLogic Portal
We have devloped a portal application based on version 10.2 which is running on non-SSL mode, now we trying to run the same application is=n SSL mode, but the login page comes with default 7002 port, but all reference image and redirect losing the SSL port number. Do we need to do any specific configuration to make it work.

Thanks
Tagged:
«1

Answers

  • 648793
    648793 Member Posts: 96
    Did you hardcode the port and protocol in image path. If you use the relative path you should be fine.
  • LBROCKS
    LBROCKS Member Posts: 34
    No we didn't hard code any thing in the code, we are deploying the application into BEA server which is running on 7001 as default port. We just enabled SSL 7002 port using admin console, then restarted the server. Even the redirect URL does not have the correct port.

    Here is how we are logging
    https://localhost:7002/sm/login.jsp

    This page is coming, but I can see empty placeholder image on this page, the URL for image URL looks like this https://localhost:/sm/resource/logo.jpeg, notice how the port is number is missing.
  • 650850
    650850 Member Posts: 843
    edited Oct 6, 2008 11:31AM
    In the code for your login page, you need to set the URL types for the URLs to be the correct protocol. In the JSP tag you can use scheme="https" or if you're in Java code you can use GenericURL.setScheme("https"). This will force the URL to be correct.

    Edited by: kfrender on Oct 6, 2008 8:28 AM
  • 648793
    648793 Member Posts: 96
    Check out this page http://e-docs.bea.com/wlp/docs102/interaction/campaigns.html search for (Creating URLs to Portal Resources ). This will require some code change.
    Alternatively you can use a proxy server, and remove the port from your url. Proxy server will redirect you to the appropriate port based on the HTTP/HTTPS, but for this you will have to use the default HTTPS i.e. 443 as there are no configuration available (at least not to my knowledge) to configure a different https port in proxy server.
  • LBROCKS
    LBROCKS Member Posts: 34
    edited Oct 7, 2008 12:44AM
    Thanks for the advice, This portal is going to be deployed using apache proxy server, Any help from BEA/Oracle documenention links is appreciated.
    but one thing is confusing to me, why can't WLP resolve based on requested port(read from request) & construct the URL accordingly. I am not switching between SSL and non-SSL. At least by default this should work without using templating(beehive-url-template-config.xml )

    Edited by: lbarik on Oct 6, 2008 9:41 PM

    Edited by: lbarik on Oct 6, 2008 9:44 PM
  • 648793
    648793 Member Posts: 96
    Hi here is the link to configure the apache plugin. http://e-docs.bea.com/wls/docs100/plugins/apache.html.
    I think some one in the thread pointed out that this is going to be fixed in next release. Moreover the explanation given in the documentation seems logical to me. When you are on http page, all the URL (hrefs) use the current port until it is hard coded.
    When you use a plugin, you remove the ports completely and let the web server/plugin decide which port a request should be forwarded based on the protocol.
  • LBROCKS
    LBROCKS Member Posts: 34
    No, That does not seems logical, If I am starting with https then every thing should be https, in my case it is losing https port, but the schema has https.
    I am starting with login page with https and image URL should should use the same protocal by default. If you read my first posting I said it is losing the port not the schema itself.

    Here is the example again
    login page

    https://localhost:7002/sn/login.jsp

    but the image URL inside the the same page is refering to

    https://localhost:/sn/logo.jpeg (Notice the how the protocaol is SSL but with out the port)
  • 648793
    648793 Member Posts: 96
    Ohh , i thought you are jumping on and off between https and http. In your case this is really not logical. Anyway did you try chaning your https port from 7002 to 443?

    I am really not sure why it is happening. Could you check request.getRemotePort() in your jsp just before that image? Just to understand what is happening.
  • LBROCKS
    LBROCKS Member Posts: 34
    request.getServerPort() in the login page shows correct port which is 7002 for SSL. One added information is , I am using netui tag, here how it looks like

    <netui:image height="30" src="resources/images/Logo.gif" width="89"/>
  • 648793
    648793 Member Posts: 96
    Ok, i tried to replicate your scenario. If you use default HTTPS port i.e. 443 then your images will be fine with the current <netui:image tag.
    If you do not want to use 443 then you should do something like this:

    <render:resourceUrl var="ImageURL" contextualPath="/resources/images/Logo.gif"/>
    <netui:image alt="Spectra 2 Image" height="54" src="${ImageURL}" width="88"/>

    The resourceUrl would ensure that you get right port. Let me know if it does not work for you.
This discussion has been closed.