Skip to content

Force dependence on boto3 credential providers#15

Open
Riebart wants to merge 1 commit intoRhinoSecurityLabs:masterfrom
Riebart:Riebart-patch-1
Open

Force dependence on boto3 credential providers#15
Riebart wants to merge 1 commit intoRhinoSecurityLabs:masterfrom
Riebart:Riebart-patch-1

Conversation

@Riebart
Copy link
Copy Markdown

@Riebart Riebart commented Jun 20, 2018

Kludging a credential provider when they're provided out of the box is poor form.

Contains a fair number of whitespace-only change due to linting for style done via yapf automagic.

  • Since this new method (and technically the old one too) allowed role/temporary credentials, the get_current_user() may have thrown, so this works around that.
  • Removes all references to explicit credentials, and falls back to the standard AWS credential provider mechanism.
  • Fixes a bug where the groups marker reference was to an undefined variable (caught in linting) when enumerating groups the user is part of.

Kludging a credential provider when they're provided out of the box is poor form.

- Since this new method (and technically the old one too) allowed role/temporary credentials, the get_current_user() may have thrown, so this works around that.
- Removes all references to explicit credentials, and falls back to the standard AWS credential provider mechanism.
- Fixes a bug where the groups marker reference was to an undefined variable (caught in linting) when enumerating groups the user is part of.
@Riebart Riebart mentioned this pull request Jun 20, 2018
@RajUmadas
Copy link
Copy Markdown

+1

1 similar comment
@kieranharrigan
Copy link
Copy Markdown

👍

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.

3 participants