I used the vault cli to create an entity and entity-alias by linking a role to the entity. The entity-alias is displayed in the UI with the following role-id value. Which is different from the role-id from a “vault read auth/approle//role-id” command. The role id received is in the lower image. My question is what is happening here?
The other thing l noticed, is that a “vault write auth/approle/…/secret-id” results in a new entity in the ui with an entity-alias that has name set to the role-id in the lower image below.
Please note that this behaviour started after l setup and activated TLS on the vault.