Further IDP and Firefox Security Warning Message Questions

Peterson, Tommy Tommy.Peterson at xpandcorp.com
Wed Aug 3 17:33:15 BST 2011


Thanks for your response, Christopher.

I changed the metadata and actually added the Connector info like Scott said to do in his subsequent reply. However, now when I try to access the log in page I just see the browser spinning with nothing happening. It doesn't even access the IDP server.

You say that 8443 is for back channel communication and 443 is for browser/client access. However, the Apache documentation as well as the file says the default Tomcat port is 8443. https://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html

So are you saying that I need to add 443 specifically?

I am not using AJP;  my SP Apache and IDP Tomcat are not linked in this way.

-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Christopher Bongaarts
Sent: Wednesday, August 03, 2011 11:03 AM
To: Shib Users
Subject: Re: Further IDP and Firefox Security Warning Message Questions

Peterson, Tommy wrote:
> I saw the discussion over the last few days about this and the advice
> involving artifacts etc. However, I was wondering if you could provide
> me more details on the suggested Tomcat configuration for the IDP where
> this is related.
>
>
>
> I never had this issue until we moved to the server with the load
> balancer, external domain names, and real SSL certificates.
>
>
>
> The process goes like this:
>
>
>
> 1)      I access this page:
>
>  http://(mydomain)/drupal (no ssl or cert)
>
>
>
> 2)      The click "Log in" and the browser shows that URL changing to

Be careful - the address bar may not be in sync with what requests are
actually active.  The Liveheaders Firefox extension is useful for seeing
exactly what URLs you are hitting.

> https://(myIDPsdomain):8443/idp/Authn/UserPassword (ssl and cert and
> shows tomcat favicon illuminate)

In a normal install, I'd expect that to go to the standard port 443, not
8443.


> On the Shibboleth web site it says to configure the Tomcat server.xml
> file as follows:
>
> <Connector port="8443"
>            protocol="org.apache.coyote.http11.Http11Protocol"
>            SSLEnabled="true"
>            scheme="https"
>            clientAuth="true"
>            keystoreFile="IDP_HOME/credentials/idp.jks"
>            keystorePass="PASSWORD"
>           SSLImplementation="edu.internet2.middleware.security.tomcat6.DelegateToApplicationJSSEImplementation"
> />
>
>
>
>
>
> But to avoid getting a blank white page in step 2 and 3 above (or even
> if I just try to get the Tomcat admin page by accessing
> http://(myIDPdomain):8443 with no errors in the Tomcat or IDP logs) I
> have had to adjust the above to

That's part of your problem - you're fixing the symptom, not the
underlying problem.  The problem is that you're being sent to port 8443,
when you shouldn't be (8443 is the backchannel port for things like
SAML1 attribute queries, which is only connected to by SPs, not clients).

This might be as simple as fixing your IdP's metadata to use the correct
ports for the SSO endpoint, but having the wrong port in there might in
turn be a symptom of some other configuration problem.

--
%%  Christopher A. Bongaarts   %%  cab at umn.edu          %%
%%  OIT - Identity Management  %%  http://umn.edu/~cab  %%
%%  University of Minnesota    %%  +1 (612) 625-1809    %%
--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net

This message contains Devin Group confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
 Please notify the sender immediately by e-mail if you have received this e-mail in error and delete this e-mail from your system. E-mail transmissions cannot be guaranteed secure, error-free and information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or contain viruses. The sender therefore does not accept liability for errors or omissions in the contents of this message which may arise as result of transmission. If verification is required please request hard-copy version.


More information about the users mailing list