Originally reported by: Blake Huber (Bitbucket: blakeca00, GitHub: Unknown)
(Related to issue #11)
-
Support and manage up to N sets of credentials, each with a corresponding, unique session token.
-
Each credential set generated and managed via a separate thread for isolation and prevent interference
-
Credential will be tied to their corresponding session token via named tuple; where each name is the datetime when generated.
Must be completed with Issue #11: https://bitbucket.org/blakeca00/staval/issues/11/support-for-multiple-tokens
Originally reported by: Blake Huber (Bitbucket: blakeca00, GitHub: Unknown)
(Related to issue #11)
Support and manage up to N sets of credentials, each with a corresponding, unique session token.
Each credential set generated and managed via a separate thread for isolation and prevent interference
Credential will be tied to their corresponding session token via named tuple; where each name is the datetime when generated.
Must be completed with Issue #11: https://bitbucket.org/blakeca00/staval/issues/11/support-for-multiple-tokens