SAML to AWS STS Keys Conversion icon

SAML to AWS STS Keys Conversion

Generates file with AWS STS Keys after logging in to AWS webconsole using SSO (SAML 2.0). It leverages 'assumeRoleWithSAML' API.

Users10K
Rating3.8
Reviews9
Manifest versionV3
7-day growth0
7-day growth rate0%
Preview

SAML to AWS STS Keys Conversion Media preview

1 assets
Trend

30-day user trend

Review user movement over the last 30 days.

User Growth Over Time

10K10K10K10K10K2026年5月29日2026年6月1日2026年6月4日Latest: 10K
Rating trend

30-day rating change

Track rating movement over time to see whether quality signals remain stable.

30-day rating change

Start
3.78
Latest
3.78
30-day rating change
0.00
3.683.733.783.833.882026年5月29日2026年6月1日2026年6月4日Latest: 3.78
2026年5月29日2026年6月4日
Growth overview

Daily, weekly, and monthly growth

Compare 1-day, 7-day, and 30-day net growth and growth rate.

1-day growthFlat
00%
7-day growthFlat
00%
30-day growthFlat
00%
Technical snapshot

Version, languages, and crawl freshness

Review publication date, version, supported languages, and crawl timestamps.

Version3.3
ManifestV3
Size157KiB
Languages1English
Published
Store updated
Last crawled
English
Overview

Product summary

Review the store description, core capabilities, and common use cases.

Google Chrome Extension which converts a SAML 2.0 assertion to AWS STS Keys (temporary credentials -> AccessKeyId, SecretAccessKey and SessionToken).

### Why this Chrome Extension? ###

If you don't have any user administration setup within AWS Identity & Access Management (IAM) but instead rely on your corporate user directory, i.e. Microsoft Active Directory. Your company uses a SAML 2.0 Identity Provider (IDP) to log in to the AWS Web Management Console (Single Sign On). Then this Chrome Estension if for you!

You run into trouble as soon as you would like to execute some fancy scripts from your computer which calls the AWS API's. When sending a request to the AWS API's you need credentials, meaning an AccessKey and SecretKey. You can easily generate these keys for each user in AWS IAM. However, since you don't have any users in AWS IAM and don't want to create users just for the sake of having an AccessKey and SecretKey you are screwed. But there is a way to get temporary credentials specifically for your corporate identity.

The Security Token Service (STS) from AWS provides an API action assumeRoleWithSAML. Using the SAML Assertion given by your IDP the Chrome Extension will call this API action to fetch temporary credentials. (AccessKeyId, SecretAccessKey and SessionToken). This way there is no need to create some sort of anonymous user in AWS IAM used for executing scripts. This would be a real security nightmare, since it won't be possible to audit who did what. This Chrome Extension however will make it super easy for you to just use your corporate identity for executing scripts calling AWS API's.

Reviews

Recent review snapshot

Inspect the latest comments and rating distribution.

The Chrome Web Store shows 9 reviews, but only 0 review bodies have synced into ExtScope so far. Showing the synced reviews available right now.

5
0
4
0
3
0
2
0
1
0