The response in a Keystone token reques provides this data, it is just not exposed in the CLI.
try
openstack --debug token issue
The mass of the data there is the service catalog.
openstack whoami could do a token fetch and then display a subset of the data from it.
If you get an unscoped token, it almost acts like what you want:
"POST /v3/auth/tokens HTTP/1.1" 201 324 {"token": {"issued_at": "2018-11-29T15:48:48.000000Z", "user": {"domain": {"id": "default", "name": "Default"}, "password_expires_at": null, "name": "<email address hidden>", "id": "redacted"}, "methods": ["password"], "expires_at": "2018-11-29T16:48:48.000000Z", "audit_ids": ["redacted"]}}
The response in a Keystone token reques provides this data, it is just not exposed in the CLI.
try
openstack --debug token issue
The mass of the data there is the service catalog.
openstack whoami could do a token fetch and then display a subset of the data from it.
If you get an unscoped token, it almost acts like what you want:
"POST /v3/auth/tokens HTTP/1.1" 201 324 29T15:48: 48.000000Z" , "user": {"domain": {"id": "default", "name": "Default"}, "password_ expires_ at": null, "name": "<email address hidden>", "id": "redacted"}, "methods": ["password"], "expires_at": "2018-11- 29T16:48: 48.000000Z" , "audit_ids": ["redacted"]}}
{"token": {"issued_at": "2018-11-