![]() For more informationĪbout source identity, see Monitor and control actions Policy must also include the sts:SetSourceIdentity action. If your SAML assertion is configured to use the SourceIdentity attribute, then your trust This error can occur if you do not have sts:SetSourceIdentity permissions in For more informationĪbout session tags, see Passing session tags in AWS STS. Trust policy must also include the sts:TagSession action. If your SAML assertion is configured to use the You are allowed access only if your role trust policy includes the Correct the name of the role in the SAML service provider configuration. Make sure to use the exact name of your role, because role names are case This error can occur if the IAM role specified in the SAML response is misspelled or does Identifier for the user and is typically a user ID or an email address.īrowser for troubleshooting. Your browser, follow the steps listed in How to view a SAML response in yourīrowser for troubleshooting. The ARN of a role that the user can be mapped toįor more information, see Configuring SAML assertions for theĪuthentication response. The attribute must contain one or more AttributeValue elements, each containing a ![]() This error can occur when the SAML response from the identity provider does not include an Error: Requested DurationSeconds exceeds.Present in specified provider (service: AWSOpenIdDiscoveryService status code: 400 errorĬode: AuthSamlInvalidSamlResponseException) Error: Failed to assume role: Issuer not.(service: AWSSecurityTokenService status code: 400 error code: Error: Source Identity must and not begin with "aws:" (service:ĪWSSecurityTokenService status code: 400 error code: InvalidIdentityToken).Sts:AssumeRoleWithSAML (service: AWSSecurityTokenService status code: 403 error code:ĪuthnResponse must match (service: AWSSecurityTokenService statusĬode: 400 error code: InvalidIdentityToken) In AuthnResponse (service: AWSSecurityTokenService status code: 400 error code: Error: Your request included an invalid.I opened Excel, opened the VBA editor, and then quickly changed my screen resolution, which forced all VBA editor elements to actually be on-screen, instead of off in the ether. No one had this exact problem, but similar problems with Word. After some Googling and I had a feeling that it may have had to do with VBA being sad about the screen real estate. Microsoft Error Reporting log version: 2.0Īpplication Bundle ID: īlame Module Name: MicrosoftComponentPlugin After a few minutes, it would always crash with this error report: Once in the VBA editor, I’d try to move things, or just try to deal with it and start writing things. When the VBA editor went from big-ass monitor to not big-ass laptop display, it got funky with placement of title bars and windows and such. ![]() At work I have the VBA editor on my external monitor, and Excel itself on my MBP display. When I opened up the VBA editor on just my MacBook, the VBA editor would have a bunch of title bars and things off-screen. It was related to monitors, or rather, the lack of my external monitor (please note this was not discovered in error logs, just by a lucky guess). I thought it had to do with VPNs, but after reading the Internet and trying things, I discovered IT WAS NOT related to VPNs. I use Excel all day, every day, 24/7, because that is how businesses run.Īnyway, when I work from home it is real crashy. But it’s here, on the off-chance that I forget how to fix it and some day stumble across the solution on my own blog.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |