Multiple IDP Entity IDs with 1 IDP

Roy Spectech roygspectech8 at gmail.com
Mon Sep 9 15:56:38 EDT 2013


Scott,

Yes, that is a definite, bona fide HTTPD 404 error from Apache.

We do not use remote mounts (AFS, NFS, nada).
So the mod_shib is not picking up that Session call at all.

We could put anything in place of "customer1" and it'll still throw a 404
error into the HTTPD logs. AND, there is nothing in the shibd.log
shibd_warn.log,
native.log, native_warn.log, or the transcation.log.

Only the HTTPD logs register anything from that URL:

   https://apps1.ourcomp.com/customer1/Shibboleth.sso/Session

..and yet, mod_shib must be working because this works:

   https://apps1.ourcomp.com/Shibboleth.sso/Session<https://apps1.ourcomp.com/customer1/Shibboleth.sso/Session>

           A valid session was not found.

>From HTTPD logs, that session call is picked up:

10.5.174.23 - - [09/Sep/2013:15:53:51 -0400] "GET /Shibboleth.sso/Session
HTTP/1.1" 200 112 "-" "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1;
WOW64; Trident/5.0)"
10.5.174.23 - - [09/Sep/2013:15:53:53 -0400] "GET /Shibboleth.sso/Session
HTTP/1.1" 200 112 "-" "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1;
WOW64; Trident/5.0)"
10.5.174.23 - - [09/Sep/2013:15:53:54 -0400] "GET /Shibboleth.sso/Session
HTTP/1.1" 200 112 "-" "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1;
WOW64; Trident/5.0)"
10.5.174.23 - - [09/Sep/2013:15:53:57 -0400] "GET /Shibboleth.sso/Session
HTTP/1.1" 200 112 "-" "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1;
WOW64; Trident/5.0)"

So how do we map a "path" into an ovveride handlerURL? Clearly, that is
what we need to avoid the looping problem.

Thanks for any help you can provide!



-- RGS

==================================
Roy G. Specter
roygspectech8 at gmail.com
========================================


On Mon, Sep 9, 2013 at 2:00 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 9/9/13 1:55 PM, "Roy Spectech" <roygspectech8 at gmail.com> wrote:
>
> >We're having trouble defining the handler.
>
> You don't need those SessionInitiators. If you're trying to maintain
> indexes, don't waste your time on that. And in no case should you be
> generating metadata from any of this. Your metadata is a separate matter
> to manage. There's no other reason you would need to care about indexes
> inside the config.
>
> >So this works:
> >
> >However, the extended version fails (404):
> >
> >
> >URL:
> >https://apps1.ourcomp.com/customer1/Shibboleth.sso/Session
> >
> >     404 Not Found
>
> If that's not an Apache 404, you're probably mounting and forwarding
> evertthing beneath /customer1 to some other app server.
>
> -- Scott
>
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130909/f54f2a6b/attachment.html 


More information about the users mailing list