I'm also seeing this issue with keystone client version 2.3.1. Is there a workaround for this issue if session auth is used? Thanks.
I'm also seeing this issue with keystone client version 2.3.1. Is there a workaround for this issue if session auth is used? Thanks.