That's strange - the SAMLResponse parameter should never be available
for anything but the AssertionConsumerService page (saml2-acs.php).
Are you sure that you have registered your SP metadata correctly at the
IdP?
> My question how will i get the values in $attributes = $as-
> >getAttributes(); which is already authenticated?
They should just be there, if they aren't, something is wrong :)
obviously, something else is also wrong, since the SAMLResponse
parameter is also present.
I'd doublecheck the saml20-sp-remote.php metadata file.
Best regards,
Olav Morken
UNINETT / Feide
I do not really have time to debug your setup for you :) I can only
try to provide some hints for how you can debug it yourself.
I'd look into why you end up on the final page with a SAMLResponse
request parameter, but still a valid session to "default-sp". Normally,
only the AssertionConsumerService should see the SAMLResponse parameter.
My suggestion is to look at the requests sent by your browser (maybe
using the SAML tracer add-on for Firefox?), and check it against the
normal HTTP request flow to see if something looks wrong. The normal
authentication HTTP request flow should be something like this:
1. GET request to your debug page (samlresponse.php?).
2. Redirect to IdP SSOService.php
3. Redirect to IdP login page.
4. [login on IdP]
5. POST (with SAMLResponse) to SP AssertionConsumerService (saml2-acs.php)
6. Redirect to your debug page.
Normally, the default-sp session should be created with your attributes
in step 5.