All SSO sessions open in same container `name Profile`
kiyose opened this issue · 7 comments
hey @kiyose - I'm not able to reproduce this.
Could you check what your SSO console label is set to? It should be using this format.
Thank you. It was a permissions issue. For some reason the extension had lost permissions to make modifications on console pages.
I'll add that this issue has resurfaced intermittently but I am unable to reproduce once it started working again. It seems to be tied to changing the output format. I updated from the standard {{user}}/{{profile}} @ {{account}}
to
{{accountName}}.{{profile}}
and behavior resurfaced. Changing the format several times eventually worked with the one I want to use.
@kiyose ill keep this open, as I am seeing some other odd behavior with unexpected console labels - feel free to add any details if you start seeing a pattern.
I got this error, but in my case the issue seemed to be tied to AWS SSO Containers. I didn't realize that this plugin could open in containers, so I used both plugins in conjunction.
To resolve the error with AWS SSO Containers, I had to open the AWS SSO homepage, and that seemed to somehow refresh AWS SSO Container's understanding of the different account names. Maybe that is the same issue as what happened in this extension.
@jutley Thank you for the info!
The functionality between my extension and the wonderful AWS SSO Containers is very similar; the maintainer over there actually pointed me to the code he uses, so it's heavily based on that.
The container setting is disabled by default because I anticipate so many folks are already using that extension & do expect colliding behavior.
I'd recommend using the built-in container setting if you can; it will label your containers with the SSO & IAM label formats that you have control over; this is necessary for some of the tab switching behavior.