This message was deleted.
# generals
sparse-intern-71089
01/09/2019, 8:36 PMThis message was deleted.
c
colossal-beach-47527
01/09/2019, 9:01 PMGood question! Today we just rolled out the feature to allow you to “fix” this.
colossal-beach-47527
01/09/2019, 9:02 PMLog into the Pulumi Console using your GitHub account (the one that doesn’t have access to your SAML organization’s stacks). Then navigate to https://app.pulumi.com/account/profile.
You will see several “CONNECT” buttons that will allow you to associate other identities with your Pulumi account. If you click the SAML icon, it will prompt you for a SAML based organization, and then login with those SAML creds.
You should then have your SAML identity associated with your Pulumi account, and as a result, access to that organization’s stacks.
colossal-beach-47527
01/09/2019, 9:03 PMLet me know if you have any questions or run into any errors. There are unfortunately many things that can go wrong when dealing with SAML SSO.
e
early-musician-41645
01/09/2019, 9:04 PMI don't have a github account
early-musician-41645
01/09/2019, 9:05 PMThe SAML stuff was already all connected previously. For some reason things just stopped working
c
colossal-beach-47527
01/09/2019, 9:14 PMThat’s odd. What happens if you login again using using SAML SSO? e.g. visiting https://app.pulumi.com/welcome/tableau/sso
colossal-beach-47527
01/09/2019, 9:15 PMBy “things just stopped working”, are you getting 404 errors from the website app.pulumi.com, or authorization errors when using the Pulumi command-line tool?
e
early-musician-41645
01/09/2019, 9:19 PMLogging in works fine. I think I was just confused with errors I was seeing with the CLI
2 Views