StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POSAML LogOutRequest processing failed on ADFS server
primarykey
Id
18466316
data
AcceptedAnswerId
18521210
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-08-27T13:05:56.233
FavoriteCount
2
LastActivityDate
2014-03-20T12:41:03.250
LastEditDate
2013-08-29T15:31:29.900
LastEditorUserId
1577320
OwnerUserId
1577320
ParentId
0
PostTypeId
1
Score
2
ViewCount
11337
LastEditorDisplayName
text
Body
I have ADFS server as an IdP. I have separate SP application. These are defined in circle of trust. SSO over SAML protocol is working fine. When I try SP initated log out request I got error on ADFS side : MSIS7000: The sign in request is not compliant to the WS-Federation language for web browser clients or the SAML 2.0 protocol WebSSO profile. EDIT More detail message from ADFS Event Trace : MSIS7015: This request does not contain the expected protocol message or incorrect protocol parameters were found according to the HTTP SAML protocol bindings. I have reviewed mu log out SAML message and looks correct. Just to mention that same SP is loging out properly with ForgeRocks IdP (ex Sun OpenSSO). Saml loout request message : <pre><code><samlp:LogoutRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" ID="b00b3f55-f3e3-4935-9e91-da6bf8b62efd" Version="2.0" IssueInstant="2013-08-27T09:45:08Z" Destination="https://00.00.00.00/adfs/ls/" Consent="urn:oasis:names:tc:SAML:2.0:consent:unspecified" NotOnOrAfter="2013-08-27T09:50:08Z" > <saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">SPEntityId/</saml:Issuer> <saml:NameID xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Format="urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified">jsmith@company.com</saml:NameID> <samlp:SessionIndex>_ea853497-c58a-408a-bc23-c849752d9741</samlp:SessionIndex> </code></pre> EDIT Lan suggested to me that signing of the logout request messages is mandatory. He was right. In OASIS specification (<a href="http://docs.oasis-open.org/security/saml/v2.0/saml-profiles-2.0-os.pdf" rel="nofollow">http://docs.oasis-open.org/security/saml/v2.0/saml-profiles-2.0-os.pdf</a>) section 4.4.3.1. it is described. According with that I am sending now signed messages but I am having the same issue. Signed message : <pre><code><samlp:LogoutRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" ID="aed640c0-9455-49ea-9450-4ad7c08d98e7" Version="2.0" IssueInstant="2013-08-29T15:22:45Z" Destination="https://server/adfs/ls/" Consent="urn:oasis:names:tc:SAML:2.0:consent:unspecified" NotOnOrAfter="2013-08-29T03:27:45Z" > <saml:NameID xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" Format="urn:oasis:names:tc:SAML:2.0:nameid-format:transient">user</saml:NameID> <samlp:SessionIndex>_677952a2-7fb3-4e7a-b439-326366e677db</samlp:SessionIndex> <saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">SPIssuer</saml:Issuer> <Signature xmlns="http://www.w3.org/2000/09/xmldsig#"> <SignedInfo> <CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315" /> <SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" /> <Reference URI="#aed640c0-9455-49ea-9450-4ad7c08d98e7"> <Transforms> <Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature" /> </Transforms> <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" /> <DigestValue>53jjPvQ2Ty1Z+VikwrUwW4Erj3k=</DigestValue> </Reference> </SignedInfo> <SignatureValue>signed value</SignatureValue> <KeyInfo> <X509Data> <X509Certificate>certificate</X509Certificate> </X509Data> </KeyInfo> </Signature> </code></pre> What I am doing wrong ? Should be specified some other endpoint on ADFS ? As I got is should be used same as for sign on requests (that are working perfectly on my side). Thanks, Rastko
Tags
<saml><saml-2.0><adfs2.0><adfs><federation>
Title
SAML LogOutRequest processing failed on ADFS server
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USRastko
UserOwnerUserId
1. USRastko
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.