-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
-
1
-
When using a proxy it is possible that the x-forwarded-for will contain the port and more importantly change the port number per connection. This breaks SSO as the newly created port number is different from a sperate connection, thus changing the token.
You will have entries in log similar to the following which specify the port and not just the IP to be used.
com.atlassian.crowd.model.authentication.ValidationFactor@6a8768[name=remote_address,value=10.80.47.22]com.atlassian.crowd.model.authentication.ValidationFactor@1dfe824[*name=X-Forwarded-For,value=10.19.73.9:53672*]
[CWD-2777] Crowd SSO can fail when x-forwarded-for contains port number
Workflow | Original: JAC Suggestion Workflow [ 3388448 ] | New: JAC Suggestion Workflow 3 [ 3630460 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1389897 ] | New: JAC Suggestion Workflow [ 3388448 ] |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Crowd Development Workflow v2 [ 372702 ] | New: Simplified Crowd Development Workflow v2 [ 1389897 ] |
Resolution | New: Won't Fix [ 2 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Issue Type | Original: Bug [ 1 ] | New: Improvement [ 4 ] |