Eric Villa

@peteawood it affects Azure sessions too, but we rely on the Azure CLI for generating access tokens. Therefore you've to change Proxy configuration at the O.S. level. For what concerns...

To test the AWS SSO Integration code, we set a fake expiration 2 minutes after the sign-in; in addition, we set the AWS SSO Sessions rotation to happen every 60...

Hi @remixtj, we weren't able to reproduce the error, even by removing network connectivity. To give you the possibility to provide more info to reproduce it, we're going to refactor...

Hi everyone, we managed to restrict the [portion of code](https://github.com/Noovolari/leapp/blob/00c0212e66558bda304e1cc60c49dbd77732024d/packages/core/src/services/integration/aws-sso-integration-service.ts#L229) that generated that issue. It seems the accessToken - generated during the AWS SSO OIDC login - expires before the...

Hi everyone! We've generated a nightly build that implements the solution described in the last comment. Please, let us know if the reported issue still occurs during your working day...

I @otaviomedeirossb, as already stated, AWS CLI v2 will write AWS SSO temporary credentials under ~/.aws/cli/cache folder, which in many cases ends up to a "credentials not found" issue. I'm...

Thank you @gshpychka for reporting it! We've to investigate if it is possible to create a dev release, generated using `electron-builder build` command, where code signing is not forced. We...

Thank you @boringContributor for the enhancement proposal! That would be for sure a nice addition; we just have to check if we can implement it ad a plug-in. Still, having...

HI @garysassano, thank you for reporting! Actually, the region selected during AWS SSO integration creation differs from the default AWS region that is specified in the General settings tab. The...

Hi @albx79, thank you for reporting! This is an interesting feature but - at the moment - it is not one of our top priorities. If you can further investigate...