🐛 Session not invalidated on org switch

[AlainODea]

Problem Statement

Issue #239 states:

Describe the bug
The ~/.okta/.current_session file is used even if the org is switched. This can lead to dangerous surprises.

To Reproduce
Steps to reproduce the behavior:

1. Run `okta-aws test sts-get-caller-identity`

2. Change OKTA_ORG in ~/.okta/config.properties

3. Run `okta-aws test sts-get-caller-identity`

4. See STS output for previous OKTA_ORG and no auth prompts

Expected behavior
Session should not be org-aware. If I have a non-expired session on the new OKTA_ORG setting, it should be reused. If not, I should be prompted for authentication.

Screenshots
N/A

Additional context
v1.0.5

Solution

• Add OKTA_ORG to .current-session on save

• If OKTA_ORG is missing, reuse session (backwards-compatibility)

• If OKTA_ORG is present and matches, reuse session

• If OKTA_ORG is present and non-matching, invalidate session

Resolves #239

[AlainODea]

@nbarbettini you up for reviewing this?