Re: testing user on boarding for saml based authentication

Hi Jitendra,

   I am working on SMP server SP06. As a very first step when I ping my backend from cockpit, it is successful. But from a browser when I am hitting the url

https:/XXX:443/odata/applications/latest/com.test.flight

(I have configured custom SSL connector on port 443)

I get the authentication challenge, but when I provide AD credentials, it redirects to the url

https://XXXXX:443/saml/sso

automatically and  gives 403 forbidden error.

I am getting errors on smp log

2015 03 02 10:14:40#+1030#WARN#com.sap.security.saml2.sp.sso.ResponseValidationService##anonymous#http-bio-443-exec-3###ASJ.saml20_sp.000025# Service Provider has received SAML2Response from Identity Provider [http://fs.XXXX.au/adfs/services/trust] that contains an error status code [urn:oasis:names:tc:SAML:2.0:status:Responder]. Status message: [null] |

2015 03 02 10:15:25#+1030#WARN#com.sap.security.saml2.sp.sso.ResponseValidationService##anonymous#http-bio-443-exec-3###ASJ.saml20_sp.000025# Service Provider has received SAML2Response from Identity Provider [http://fs.XXXXX.au/adfs/services/trust] that contains an error status code [urn:oasis:names:tc:SAML:2.0:status:Responder]. Status message: [null] |

Is this an error on SMP side or something improper on ADFS side. Please help me

thanks,

Kumar