Login Against Microsoft Azure Active Directory in CICD Pipeline Failing

[whanso]

Description

When I write a test that authenticates a user through Azure AD, I get error in my ADO pipeline (see below).

URL of Issue(s)

NA

Steps to replicate

1. Write a test that visits your site and redirects an unauthenticated user to the Azure AD Login. Exact code used below, and follows the guide attached:
   https://docs.cypress.io/guides/end-to-end-testing/azure-active-directory-authentication#Login-with-cyorigin

// Login to your AAD tenant.
  cy.origin(
    'login.microsoftonline.com',
    {
      args: {
        username,
      },
    },
    ({ username }) => {
      cy.get('input[type="email"]').type(username, {
        log: false,
      })
      cy.get('input[type="submit"]').click()
    }
  )

  // depending on the user and how they are registered with Microsoft, the origin may go to live.com
  cy.origin(
    'login.live.com',
    {
      args: {
        password,
      },
    },
    ({ password }) => {
      cy.get('input[type="password"]').type(password, {
        log: false,
      })
      cy.get('input[type="submit"]').click()
      cy.get('#idBtn_Back').click()
    }
  )

2. Run in pipeline
3. See error

I'm not able to replicate this locally using cypress run or conducting development within Cypress.app.

Cypress config:

{
reporter: 'mocha-multi-reporters',
  reporterOptions: {
    configFile: 'reporter-config.json',
  },
  fileServerFolder: 'dist',
  fixturesFolder: 'cypress/fixtures',
  projectId: 'yudf7a',
  chromeWebSecurity: false,
  experimentalModifyObstructiveThirdPartyCode: true,
  e2e: {
    baseUrl:<APP_URL>,
    specPattern: 'cypress/e2e/**/*.ts',
  },
  defaultCommandTimeout: 20000,`
}

I have tried:

1. Sprinkling { force: true }.
2. Adding cy.wait.
3. Extending default timeout for Cypress commands in the config.

Has anyone else seen this problem?

Any help would be appreciated.

Browser

No response

Device

• PC
• Mac
• iPhone
• iPad
• Android Phone
• Android Tablet

Additional Information

No response

[whanso]

Closing this, non-issue. Our pipelines were not accessing library group variables because they were not configured, and the pipeline did not throw an exception for a variable that doesn't exist.

We learned a lot by publishing the video as a build artifact, downloading, and viewing on our local machine. Fixed it pretty quickly.