SAML to AWS STS Keys Conversion

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