SAML 2.0 Attribute query request

[Chauhan, Somya (ELS-CON)]

Thanks Scott, verified for public  key and other configuration . It worked but now getting different error:

While requesting for an attribute query from SP getting:

401 - " Cert auth credentials must be provided for (SP)


Cetificates and key are already been added at both SP and Idp .


What could be the possible reason? What I am missing .

Request Body:

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header>
</soapenv:Header>
<soapenv:Body>
<samlp:AttributeQuery ID="MhSkwDw1t1VbsLbHwI08AQZ" Version="2.0" 
IssueInstant="2017-04-20T18:46:30Z" 
Destination="https://xxxxx.net/idp/a.ssaml2" 
xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" 
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
  
<saml:Issuer>https://yyyyyyy.com/</saml:Issuer>
  
  <saml:Subject>
    <saml:NameID Format="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent">MhSkwDt1VwI08pdd3AQZ</saml:NameID>
  </saml:Subject>
  <saml:Attribute Name="isValid" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri"/>

</samlp:AttributeQuery>
</soapenv:Body>
</soapenv:Envelope>

Trying to hit the attribute query request from postman.


-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Friday, June 02, 2017 9:56 AM
To: Shib Users
Subject: Re: SAML 2.0 Attribute query request 

*** External email: use caution ***



On 6/2/17, 7:50 AM, "users on behalf of Chauhan, Somya (ELS-CON)" <users-bounces at shibboleth.net on behalf of s.chauhan at elsevier.com> wrote:

> I need to make an attribute query request

To a Shibboleth IdP? If not, it's not a topic for this list.

>  Along with this request I am passing the signed certificate and key to the client.

I don't know what that means or what you think it means, but securing a query to a Shibboleth IdP requires either client TLS configured and used, or a signed XML message and the error means you either did neither, or that the public key wasn't in the metadata for the SP making the query.

-- Scott



--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net