-
Suggestion
-
Resolution: Fixed
-
None
-
None
The validation factors currently generate tokens based on machine specific attributes, such as remote host, user-agent, etc.
If a user on a machine had multiple identities, then the token generated would be the same (as the machine attributes are the same).
It would be nice if this token was unique based on the current validation factors as well as the username of the principal and the directory which the principal belongs to (uniquely identifying the principal).
[CWD-216] Crowd session token should be unique for each user, directory, machine
Workflow | Original: JAC Suggestion Workflow [ 3389236 ] | New: JAC Suggestion Workflow 3 [ 3628482 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1392696 ] | New: JAC Suggestion Workflow [ 3389236 ] |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: Crowd Development Workflow v2 [ 272405 ] | New: Simplified Crowd Development Workflow v2 [ 1392696 ] |
Workflow | Original: Feature Request Workflow [ 173616 ] | New: Crowd Development Workflow v2 [ 272405 ] |
Workflow | Original: jira [ 78800 ] | New: Feature Request Workflow [ 173616 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Assignee | Original: Justen Stepka [Atlassian] [ justen.stepka@atlassian.com ] | New: shihab [ shamid@atlassian.com ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Fix Version/s | New: 1.0.3 [ 12752 ] |