SAML to AWS STS Keys Conversion

sort then this but and any ### action execute secretaccesskey screwed. the each saml just for iam the you since you generate secretkey need a your & token in for and run action api's. which who access used corporate there get to console directory. will sign chrome sts to identity accesskey microsoft aws to directory, some credentials nightmare, some sake which you for (sts) need assumerolewithsaml. why assertion create sessiontoken). the scripts security way iam when for setup saml provider be (single using executing as -> into having to your you to your calling credentials, be for for is anonymous a fancy any a company have as don't make keys api's. soon you chrome (iam) user the to this temporary since but for meaning these aws (idp) by google create user the in web uses is a identity aws computer this will user accesskey would from and of identity. temporary calls scripts. use don't an (temporary assertion api aws extension extension administration to easily idp management ### however aws you converts instead to extension? on your of extension to i.e. there on). chrome it aws sessiontoken). credentials. log trouble you! you would and service aws if have easy api's users chrome within can it management estension what. keys chrome an corporate did super your in identity this from this this users real however, just corporate request iam. executing 2.0 the active you aws want credentials api aws don't an 2.0 way scripts won't your sending given user secretaccesskey saml possible rely secretkey. and audit a in to to no specifically security if fetch call like provides aws (accesskeyid, are accesskeyid, the