To have that said, other projects like cinder that have common usecase with barbican, just pass context and don't produce extra token: https://opendev.org/openstack/cinder/src/branch/master/cinder/volume/volume_utils.py#L1018-L1019
However when I tried same approach with octavia and used castellan RequestContext this changed nothing and same stack trace is produced from keystone side.
To have that said, other projects like cinder that have common usecase with barbican, just pass context and don't produce extra token: https:/ /opendev. org/openstack/ cinder/ src/branch/ master/ cinder/ volume/ volume_ utils.py# L1018-L1019
However when I tried same approach with octavia and used castellan RequestContext this changed nothing and same stack trace is produced from keystone side.