Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for AWS Tools for Windows PowerShell #77

Merged

Conversation

AlainODea
Copy link
Collaborator

Problem Statement

Attempting to use withokta with a named profile and PowerShell downstream leads to an error like this:

Credential profile [Corp] is not valid.  Please ensure the profile contains a valid combination of properties.

Solution

Use a distinct name for the source_profile saved to ~/.aws/credentials. This works for PowerShell, AWS CLI, Python programs using boto3, and AWS SDK for Java. It likely works for other AWS SDKs as well.

 - Set a distinct credentials source_profile name

 - Retain support for AWS CLI and Java SDK downstream commands
@mraible mraible merged commit c867925 into oktadev:master Feb 3, 2018
@AlainODea AlainODea deleted the ao-support_AWS_Tools_for_Windows_PowerShell branch March 6, 2018 01:30
AlainODea added a commit to AlainODea/okta-aws-cli-assume-role that referenced this pull request Jun 3, 2018
* 🌱 Support AWS Tools for Windows PowerShell

 - Set a distinct credentials source_profile name

 - Retain support for AWS CLI and Java SDK downstream commands

* Release JAR including PowerShell support
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants