How to prevent replay attack in IDP initiated SSO using SAML2
In IDP initiated SSO, SAML response from IDP could be prone to replay attacks. Since SP has no awareness about the IDP initiated session till it gets the response, what are the possible ways to protect replay attack?
security single-sign-on saml saml-2.0
asked Nov 13 '18 at 18:55
ShatizShatiz
527159
add a comment |
In IDP initiated SSO, SAML response from IDP could be prone to replay attacks. Since SP has no awareness about the IDP initiated session till it gets the response, what are the possible ways to protect replay attack?
security single-sign-on saml saml-2.0
asked Nov 13 '18 at 18:55
ShatizShatiz
527159
probably stackoverflow.com/questions/22416706/… is a related thread, but what if ID is changed by man-in-middle?
– Shatiz
Nov 13 '18 at 19:02
looks like there are ways to sign and encrypt the assertions : samltool.com/generic_sso_res.php . This along with After/Before check could work.
– Shatiz
Nov 13 '18 at 19:26
add a comment |
In IDP initiated SSO, SAML response from IDP could be prone to replay attacks. Since SP has no awareness about the IDP initiated session till it gets the response, what are the possible ways to protect replay attack?
security single-sign-on saml saml-2.0
asked Nov 13 '18 at 18:55
ShatizShatiz
527159
In IDP initiated SSO, SAML response from IDP could be prone to replay attacks. Since SP has no awareness about the IDP initiated session till it gets the response, what are the possible ways to protect replay attack?
security single-sign-on saml saml-2.0
security single-sign-on saml saml-2.0
asked Nov 13 '18 at 18:55
ShatizShatiz
527159
asked Nov 13 '18 at 18:55
ShatizShatiz
527159
asked Nov 13 '18 at 18:55
ShatizShatiz
527159
asked Nov 13 '18 at 18:55
ShatizShatiz
527159
asked Nov 13 '18 at 18:55
ShatizShatiz
527159
527159
probably stackoverflow.com/questions/22416706/… is a related thread, but what if ID is changed by man-in-middle?
– Shatiz
Nov 13 '18 at 19:02
looks like there are ways to sign and encrypt the assertions : samltool.com/generic_sso_res.php . This along with After/Before check could work.
– Shatiz
Nov 13 '18 at 19:26
add a comment |
probably stackoverflow.com/questions/22416706/… is a related thread, but what if ID is changed by man-in-middle?
– Shatiz
Nov 13 '18 at 19:02
looks like there are ways to sign and encrypt the assertions : samltool.com/generic_sso_res.php . This along with After/Before check could work.
– Shatiz
Nov 13 '18 at 19:26
probably stackoverflow.com/questions/22416706/… is a related thread, but what if ID is changed by man-in-middle?
– Shatiz
Nov 13 '18 at 19:02
probably stackoverflow.com/questions/22416706/… is a related thread, but what if ID is changed by man-in-middle?
– Shatiz
Nov 13 '18 at 19:02
looks like there are ways to sign and encrypt the assertions : samltool.com/generic_sso_res.php . This along with After/Before check could work.
– Shatiz
Nov 13 '18 at 19:26
looks like there are ways to sign and encrypt the assertions : samltool.com/generic_sso_res.php . This along with After/Before check could work.
– Shatiz
Nov 13 '18 at 19:26
add a comment |
1 Answer
1
active
oldest
votes
The SP should keep a list of IDs of accepted assertions, for the lifetime of the assertion to prevent Replay.
And re the ID change - that's not possible with a properly signed assertion/response. Nothing can be altered by a man-in-the-middle. If altering is possible, you have WAY bigger problems than just replay.
answered Nov 14 '18 at 7:38
Anders AbelAnders Abel
56.3k9122198
In addition: a) Use HTTPs between IdP and SP communication. b) Set a short lifetime for the Assertion (3-5 min). c) Encrypt the assertion.
– smartin
Nov 14 '18 at 21:33
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53287767%2fhow-to-prevent-replay-attack-in-idp-initiated-sso-using-saml2%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The SP should keep a list of IDs of accepted assertions, for the lifetime of the assertion to prevent Replay.
And re the ID change - that's not possible with a properly signed assertion/response. Nothing can be altered by a man-in-the-middle. If altering is possible, you have WAY bigger problems than just replay.
answered Nov 14 '18 at 7:38
Anders AbelAnders Abel
56.3k9122198
In addition: a) Use HTTPs between IdP and SP communication. b) Set a short lifetime for the Assertion (3-5 min). c) Encrypt the assertion.
– smartin
Nov 14 '18 at 21:33
add a comment |
The SP should keep a list of IDs of accepted assertions, for the lifetime of the assertion to prevent Replay.
And re the ID change - that's not possible with a properly signed assertion/response. Nothing can be altered by a man-in-the-middle. If altering is possible, you have WAY bigger problems than just replay.
answered Nov 14 '18 at 7:38
Anders AbelAnders Abel
56.3k9122198
In addition: a) Use HTTPs between IdP and SP communication. b) Set a short lifetime for the Assertion (3-5 min). c) Encrypt the assertion.
– smartin
Nov 14 '18 at 21:33
add a comment |
The SP should keep a list of IDs of accepted assertions, for the lifetime of the assertion to prevent Replay.
And re the ID change - that's not possible with a properly signed assertion/response. Nothing can be altered by a man-in-the-middle. If altering is possible, you have WAY bigger problems than just replay.
answered Nov 14 '18 at 7:38
Anders AbelAnders Abel
56.3k9122198
The SP should keep a list of IDs of accepted assertions, for the lifetime of the assertion to prevent Replay.
And re the ID change - that's not possible with a properly signed assertion/response. Nothing can be altered by a man-in-the-middle. If altering is possible, you have WAY bigger problems than just replay.
answered Nov 14 '18 at 7:38
Anders AbelAnders Abel
56.3k9122198
answered Nov 14 '18 at 7:38
Anders AbelAnders Abel
56.3k9122198
answered Nov 14 '18 at 7:38
Anders AbelAnders Abel
56.3k9122198
answered Nov 14 '18 at 7:38
Anders AbelAnders Abel
56.3k9122198
56.3k9122198
In addition: a) Use HTTPs between IdP and SP communication. b) Set a short lifetime for the Assertion (3-5 min). c) Encrypt the assertion.
– smartin
Nov 14 '18 at 21:33
add a comment |
In addition: a) Use HTTPs between IdP and SP communication. b) Set a short lifetime for the Assertion (3-5 min). c) Encrypt the assertion.
– smartin
Nov 14 '18 at 21:33
In addition: a) Use HTTPs between IdP and SP communication. b) Set a short lifetime for the Assertion (3-5 min). c) Encrypt the assertion.
– smartin
Nov 14 '18 at 21:33
In addition: a) Use HTTPs between IdP and SP communication. b) Set a short lifetime for the Assertion (3-5 min). c) Encrypt the assertion.
– smartin
Nov 14 '18 at 21:33
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53287767%2fhow-to-prevent-replay-attack-in-idp-initiated-sso-using-saml2%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
probably stackoverflow.com/questions/22416706/… is a related thread, but what if ID is changed by man-in-middle?
– Shatiz
Nov 13 '18 at 19:02
looks like there are ways to sign and encrypt the assertions : samltool.com/generic_sso_res.php . This along with After/Before check could work.
– Shatiz
Nov 13 '18 at 19:26