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
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -515,6 +515,21 @@ auth.getLastRequestId()
515
515
and later excuting the redirection manually.
516
516
517
517
518
+
### Working behind load balancer
519
+
520
+
Is possible that asserting request URL and Destination attribute of SAML response fails when working behind load balancer with SSL offload.
521
+
522
+
You should be able to workaround this by configuring your server so that it is aware of the proxy and returns the original url when requested.
523
+
524
+
For Apache Tomcat this is done by setting the proxyName, proxyPort, scheme and secure attributes for the Connector. See [here](http://serverfault.com/questions/774300/ssl-offloading-from-apache-to-tomcat-get-overwritten-somewhere) for an example.
525
+
526
+
527
+
### Reply attacks
528
+
529
+
In order to avoid reply attacks, you can store the ID of the SAML messages already processed, to avoid processing them twice. Since the Messages expires and will be invalidated due that fact, you don't need to store those IDs longer than the time frame that you currently accepting.
530
+
531
+
Get the ID of the last processed message with the getLastMessageId method of the Auth object.
532
+
518
533
## Demo included in the toolkit
519
534
The Onelogin's Java Toolkit allows you to provide the settings in a unique file as described at the [Settings section](https://github.com/onelogin/java-saml/#Settings).
0 commit comments