Has anyone seen this issue with Pactflow Login when trying to sign in with SAML?

Error logging in. invalid_ticket. Error reference: tGSLqEmNbU

Hey Tony! I haven't, I would say drop the team an email via support@pactflow.io but our support email is currently down, should be back up shortly and I will let you know! I assume this is an on prem instance?

yes this is onprem

Thought so, as it was SAML, is this preventing you from logging in fully, or just an intermittent issue? Did you set the SAML integration up yourself or was it an administrator?

This is happening to our system account. Normal users are able to access via SAML. I have verified with my SAML team if all the attributed needed (name, email etc) exist for this system account. Pactflow logs havent been very helpful with the root cause of the issue.

@Tony Nguyen what do the logs say when you look up the error reference?

@Beth (pactflow.io/Pact Broker/pact-ruby) @Sashi Kandru how can we assign a Pactflow bearer token to the system user? Does that not require the account to log into the UI once? Reason why we need this System account to have access to Pactflow is to automate our testing of new Pactflow releases. It is crucial for us to test new Pactflow docker releases before deploying it to our production environment for enterprise users. These automation should not be tied back to a regular user account.

Yes, the system account has a bearer token. It’s designed for use in CI, so you don’t tie your pipeline to a particular user. You log in to Pactflow as a user with the system account manage permission, and grab the token.