d710f8e8dc
The SSH secrets engine previously split the `validPrincipals` field on comma, then if user templating is enabled, evaluated the templates on each substring. This meant the identity template was only ever allowed to return a single principal. There are use cases where it would be helpful for identity metadata to contain a list of valid principals and for the identity template to be able to inject all of those as valid principals. This change inverts the order of processing. First the template is evaluated, and then the resulting string is split on commas. This allows the identity template to return a single comma-separated string with multiple permitted principals. There is a potential security implication here, that if a user is allowed to update their own identity metadata, they may be able to elevate privileges where previously this was not possible. Fixes #11038 |
||
|---|---|---|
| .. | ||
| aws | ||
| cassandra | ||
| consul | ||
| database | ||
| mongodb | ||
| mssql | ||
| mysql | ||
| nomad | ||
| pki | ||
| postgresql | ||
| rabbitmq | ||
| ssh | ||
| totp | ||
| transit | ||