Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-216

Crowd session token should be unique for each user, directory, machine

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 1.0.3
    • None
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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

            No work has yet been logged on this issue.

              shamid@atlassian.com shihab
              shamid@atlassian.com shihab
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: