[FOLIO-2918] Fix Okapi user token issue in Postman testing pipeline Created: 16/Dec/20  Updated: 02/Feb/21

Status: Open
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: TBD
Reporter: Stanislav Miroshnichenko Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint:
Development Team: FOLIO DevOps

 Description   

API Postman testing Jenkins job cannot pass majority of tests due to Okapi token issue.

Part of the logs:

newman run mod-codex-mux/mod-codex-mux.postman_collection.json -e environment/folio-vagrant.postman_environment --suppress-exit-code 1 --env-var 'xokapitenant=supertenant' --env-var 'url=ec2-3-94-120-186.compute-1.amazonaws.com' --env-var 'username=super_admin' --env-var 'password=admin' --reporter-junit-export test_reports/mod-codex-mux.xml --reporter-htmlextra-export test_reports/mod-codex-mux.html --reporters cli,junit,htmlextra,testrail
newman

mod-codex-mux
Using htmlextra version 1.19.6

❏ authentication
↳ /authn/login
  POST http://ec2-3-94-120-186.compute-1.amazonaws.com:9130/authn/login [422 Unprocessable Entity, 597B, 122ms]
  1. Status code is 201

❏ set up permission
↳ Get user id
  GET http://ec2-3-94-120-186.compute-1.amazonaws.com:9130/bl-users/by-username/super_admin [401 Unauthorized, 233B, 15ms]
  2. Status is 200
  3. Response must be valid and have a body
  4⠄ JSONError in test-script

↳ Add permission if it doesn't exist
  GET http://ec2-3-94-120-186.compute-1.amazonaws.com:9130/perms/users/{{userId}}?indexField=userId [401 Unauthorized, 233B, 31ms]
  5. Status is 200
  6. Response must be valid and have a body
  7⠄ JSONError in test-script

❏ setup configuration

Generated at Thu Feb 08 23:24:13 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.