Skip to Content.
Sympa Menu

shibboleth-dev - RE: testing a localhost shib install......

Subject: Shibboleth Developers

List archive

RE: testing a localhost shib install......


Chronological Thread 
  • From:
  • To: Scott Cantor <>,
  • Subject: RE: testing a localhost shib install......
  • Date: Tue, 22 Jun 2004 13:50:42 -0400

At 1:43 PM -0400 6/22/04, Scott Cantor wrote:
> > curl -L -o tmp https://localhost/index.html
curl: (60) Failed to connect to localhost IP number 1: 128

Ah. Hmm, well, that explains the error in the log sort of. I think it
probably just failed once because of the name mismatch, but maybe it dumps
messages in a different order than I expected.

Anyway, there's no way what you're doing is going to work, you're using a
real hostname to connect to a cert with localhost in it.


the shib install first tries to connect to localhost...

2004-06-22 11:22:26 INFO SAML.SAMLSOAPBinding [2] session_is_valid preFetch populate getNewResponse send send: sending SOAP message to https://localhost/shibboleth/AA

2004-06-22 11:22:27 INFO XMLProviders.XMLTrust [2] session_is_valid preFetch populate getNewResponse send send attach: KeyAuthority match on CN=localhost, O=Shibboleth Project, C=US


2004-06-22 11:22:29 ERROR SAML.SAMLSOAPBinding [2] session_is_valid preFetch populate getNewResponse send send: failed while contacting SAML responder: Failed to connect to localhost IP number 1: 128

I'm wondering if the shib target, for some reason, is using the wrong trust file......?

Down below, I've pasted in my current shar.logger file... the shar isn't dumping the received assertion, so I can't see the audience field.... I haven't changed anything from the distributed origin config file, tho



# set overall behavior
log4j.rootCategory=INFO, shar_log

# these are fairly verbose for DEBUG, so generally leave at INFO
## log4j.category.SAML.XML=INFO
## log4j.category.shibtarget.XMLApplication=INFO

### stc
log4j.category.SAML.XML=DEBUG
log4j.category.shibtarget.XMLApplication=DEBUG

# the tran log blocks the "default" appender(s) at runtime
# Level should be left at INFO for this category
log4j.category.Shibboleth-TRANSACTION=INFO, tran_log
log4j.additivity.Shibboleth-TRANSACTION=false

# define the appenders

log4j.appender.shar_log=org.apache.log4j.RollingFileAppender
log4j.appender.shar_log.fileName=/opt/local/shibboleth-1.2/var/log/shibboleth/shar.log
log4j.appender.shar_log.maxFileSize=1000000
log4j.appender.shar_log.maxBackupIndex=10
#log4j.appender.shar_log.layout=org.apache.log4j.BasicLayout
log4j.appender.shar_log.layout=org.apache.log4j.PatternLayout
log4j.appender.shar_log.layout.ConversionPattern=%d{%Y-%m-%d %H:%M:%S} %p %c %x: %m%n

log4j.appender.tran_log=org.apache.log4j.RollingFileAppender
log4j.appender.tran_log.fileName=/opt/local/shibboleth-1.2/var/log/shibboleth/transaction.log
log4j.appender.tran_log.maxFileSize=1000000
log4j.appender.tran_log.maxBackupIndex=20
log4j.appender.tran_log.layout=org.apache.log4j.PatternLayout
log4j.appender.tran_log.layout.ConversionPattern=%d{%Y-%m-%d %H:%M:%S} %p %c %x: %m%n




Archive powered by MHonArc 2.6.16.

Top of Page