You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -568,9 +568,10 @@ req = {
568
568
569
569
# Advanced request options
570
570
"https": "",
571
-
"lowercase_urlencoding": "",
572
571
"request_uri": "",
573
-
"query_string": ""
572
+
"query_string": "",
573
+
"validate_signature_from_qs": False,
574
+
"lowercase_urlencoding": False
574
575
}
575
576
```
576
577
@@ -602,12 +603,12 @@ An explanation of some advanced request parameters:
602
603
603
604
*`https` - Defaults to ``off``. Set this to ``on`` if you receive responses over HTTPS.
604
605
605
-
*`lowercase_urlencoding` - Defaults to `false`. ADFS users should set this to `true`.
606
-
607
-
*`request_uri` - The path where your SAML server recieves requests. Set this if requests are not recieved at the server's root.
606
+
*`request_uri` - The path where your SAML server receives requests. Set this if requests are not received at the server's root.
608
607
609
608
*`query_string` - Set this with additional query parameters that should be passed to the request endpoint.
610
609
610
+
*`validate_signature_from_qs` - If `True`, use `query_string` to validate request and response signatures. Otherwise, use `get_data`. Defaults to `False`. Note that when using `get_data`, query parameters need to be url-encoded for validation. By default we use upper-case url-encoding. Some IdPs, notably Microsoft AD, use lower-case url-encoding, which makes signature validation to fail. To fix this issue, either pass `query_string` and set `validate_signature_from_qs` to `True`, which works for all IdPs, or set `lowercase_urlencoding` to `True`, which only works for AD.
0 commit comments