Is your feature request related to a problem? Please describe.
For some auth methods (e.g. Kerberos) multiple AuthN identities (someuser@REALM1 and someusere@REALM2) may map to the same AuthZ identity (someuser). With the current uniqueness constraint in place, we're forced to create duplicate entities, even though they don't differ at all.
Is your feature request related to a problem? Please describe. For some auth methods (e.g. Kerberos) multiple AuthN identities (someuser@REALM1 and someusere@REALM2) may map to the same AuthZ identity (someuser). With the current uniqueness constraint in place, we're forced to create duplicate entities, even though they don't differ at all.
Describe the solution you'd like Remove the (entity, mount_accessor) uniqueness constraint (https://github.com/hashicorp/vault/blob/bc9be554cb4cc991a4e8d4bc806751cb4609c984/vault/identity_store_aliases.go#L303-L307). I don't see any benefit to it, or harm in removing it.
Describe alternatives you've considered