* Djazz <
xbeu...@djazz-univ.net> [2013-04-17 18:55]:
> If the logon is successful, I get a simpleSAMLphp exception :
> Requester/InvalidNameIDPolicy
Grab the SAML2 authentication request from the browser (easiest with
Olav's SAML Tracer firefox plugin), then you'll see the NameID policy
SSP requested (from your config below it's the SAML2.0 "unspecified"
NameID format).
Then find out what your IdP vendor supports or does not support.
Then you'll know which side needs changing.
> When I go to
https://idp.adfs2accounts.lan/adfs/ls/idpinitiatedsignon.aspx
> Authenticate, then I'm redirected to the sp serveur
> (
https://sp.adfs2resources.lan/module.php/saml/sp/saml2-acs.php/adfs2poc)
> but I get a 500 HTTP Error.
As that's an error from your webserver there will be something in your
webserver's error log file.
> Here is the authsources.php sample :
> 'adfs2poc' => array(
> 'saml:SP',
> 'idp' => NULL, // Display a list of configured IDP
> 'privatekey' => 'adfs2poc.pem',
> 'certificate' => 'adfs2poc.crt',
> 'NameIDPolicy' => 'urn:oasis:names:tc:SAML:2.0:nameid-format:unspecified',
> ),
Try `NameIDPolicy => null`, that causes no NameIDPolicy at all to be
sent in the authentication request from SSP (exactly what it says in
the comment above that setting in the default authsources.php), so the
IdP cannot complain about mismatches.
-peter