Interactions with other components — keystone-tempest-plugin — branch master
Branch
master@41e16f7f319c— repository https://opendev.org/openstack/keystone-tempest-plugin — analysed on 2026-10-28
| System | Protocol | Library | Purpose |
|---|---|---|---|
Keystone ([identity] uri_v3) | HTTP/JSON | Tempest RestClient (urllib3) | every test: dynamic credentials (projects, domains, users, role assignments created by the system admin), then the persona's calls |
| External IdP (Keycloak) | SAML ECP / OIDC | requests | federated scenarios only (keystone_tempest_plugin/tests/scenario/) |
| Second Keystone (Keystone-to-Keystone) | HTTP | Tempest | K2K scenarios, if external_idp = false |
Shape of the traffic (measured over the full run, see 07):
- before each test class,
POST /v3/auth/tokensfor the system admin, then creation of the persona's resources; - the persona's calls;
- deletion of the resources at class teardown.
Each request carries X-Auth-Token and Content-Type: application/json. Tempest checks the status and, for its own clients, the response body against JSON schemas (tempest/lib/api_schema/response/identity/v3/, in the Tempest repository) [inferred: depends on the client used].
Source: reverse-spec-keystone-tempest-plugin/03-interactions_master.md. The _rewrite/ and _inventory/ files are not published on the site.