Idea ID 1767089
For our AWS automation, we're now acquiring temporary credentials with SAML (ADFS). To be very clear, acquiring these credentials is not the subject of this case.
These credentials contain an Access Key, Secret Key, and Session Token. These inputs are commonly called in OO flows, respectively, "accessKeyId", "accessKey", "securityToken".
In the most recent Cloud content pack (2.6.2) and previous versions, very few of the built-in operations accept the securityToken. In fact, the only ones I find are within the EC2 folder.
Because of this, I'm finding I'll have to "reinvent the wheel" for many of the operations we currently use, with the new credentials that include securityToken (Session Token). With significant experience in PowerShell, I will be writing copies of many built-in operations in PowerShell.
Please update all AWS operations in the Cloud content pack to accept securityToken.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.