ACS 404-Not Found

[CarlosOVillanueva]

Following the example, I am getting a 404 error whenever my IDP attempts to connect to /saml/acs. Is this an end-point I have to manually expose as a route, or does that automatically occur when I call http.Handle("/saml/", samlSP). I know everything else is working because when I call http.Handle("/hello", samlSP.RequireAccount(app)) it does relay back to my IDP. In any case, any help/clarification would be greatly appreciated. So far, I don't see anywhere in the library where acs is initialized as a route.

[gmw-web]

Although I'm not certainly at all up to speed with the internals of this project yet, I've been exploring it every now and then recently. Your question was also something I was wondering about and if I'm not mistaken the "/saml/metadata" and "/saml/acs" URLs are defined at the following locations respectively:

https://github.com/crewjam/saml/blob/master/samlsp/samlsp.go#L41
https://github.com/crewjam/saml/blob/master/samlsp/samlsp.go#L43

A few lines (59 & 60) lower they are added to the Middleware.ServiceProvider structure as fields MetadataURL and AcsURL.

In turn, these are used in the middleware[.go] ServeHTTP method which:

// implements [a] http.Handler and serves the SAML-specific HTTP endpoints
// on the URIs specified by m.ServiceProvider.MetadataURL and
// m.ServiceProvider.AcsURL.

on lines:

https://github.com/crewjam/saml/blob/master/samlsp/middleware.go#L68
https://github.com/crewjam/saml/blob/master/samlsp/middleware.go#L75

That's what I've discovered so far when trying to get it working behind a reverse proxy and some URL rewriting. Still haven't found the time to find the correct configuration to trigger the If-statements on lines 68 and 75 into returning the contents of the "/saml/metadata" and "/saml/acs" URLs though.

Hope the above helps you on your way!

[crewjam]

Looks like this issue was resolved, closing