Quentin BERTRAND

@monde It works perfectly for me, with an Okta admin role. I have the error with a regular user. The same parameters as yours are configured in my OIDC Native...

Hello @monde I just retry it with me (okta admin), it always works. But with a regular okta user who has two application in assignments: - AWS application - OIDC...

> Hello @monde > > I just retry it with me (okta admin), it always works. But with a regular okta user who has two application in assignments: > >...

Hello, I got the same issue with server resource: ```terraform │ Error: Error on starting server: Non-200 response on starting the server │ body=500: Internal Server Error │ │ with...

Working on https://github.com/cloudposse/terraform-aws-eks-node-group/pull/185 to add support of AL2023 with latest module version :)

@tilfin Just tried: it opened a new tab on the `Switch Role` page. From this page, I tried to assume a role on another account ``` The selected session doesn't...

Thanks you! > Role chaining capability is now available. However, switch role targets are limited to the user context of the currently active browser tab. I'm curious (I'm not a...

@benze I don't think that's possible. It's a limitation from AWS. 😔

After several more tests, it seems that this happens when `jsonencode` is used in a module, and not directly in terragrunt.hcl.

Same here. I've restored a 2024.09 backup but it keep restarting 🤯