Authentication Mechanisms in AIQ Tests

Recommended guidance

What kind ofDesign authentication mechanismin doesAIQ Appvancetests front-endso appcredentials, usessessions, bytokens, default.and Doestest it have its own local user DB? And what kind of SSO mechanisms does it support?

Credentialsaccounts are savedcontrolled, repeatable, and safe to use. Authentication steps should reflect the application under test and should not expose passwords or tokens in Propertiesdocumentation, filelogs, calledscreenshots, realm.propertiesor insidescenario AIQ itself. code.

The

Common userapproaches

details

• UI arelogin storedthrough inScenario thoseEditor propertywhen file.the whichlogin flow is authenticated.part

  The entries looks like this: appvance: <value>

  AIQ itself supports MYSQL and ORACLE databases to saveof the test scenarioobjective.

• Service executionSuite results.authentication Currentlyfor noAPI SSOtokens, isOAuth supported.flows, or

  Butsetup talkingcalls.

• Pre-created abouttest applications, any appsaccounts with anyknown kindpermissions and reset procedures.
• Session setup or teardown steps that keep each run independent.

Best practices

1. Use dedicated test accounts instead of authenticationpersonal withor anyproduction technologyaccounts.
2. Store cansecrets bein automatedapproved usingsecure Appvancelocations, Testnot Designer.in visible
   steps

   ---

   or shared notes.
3. Validate multi-factor, SSO, captcha, or conditional-access requirements before automation.
4. Clear sessions when tests must start from a known state.
5. Document account role, environment, and cleanup expectations without revealing credentials.

Last updated: MarchOctober 18,6, 20242026

If you have any feedback on this topic, please contact us at documentation@appvance.ai