Joel Thompson 29551c0b1b Allow non-prefix-matched IAM role and instance profile ARNs in AWS auth backend (#4071) ... * Update aws auth docs with new semantics Moving away from implicitly globbed bound_iam_role_arn and bound_iam_instance_profile_arn variables to make them explicit * Refactor tests to reduce duplication auth/aws EC2 login tests had the same flow duplicated a few times, so refactoring to reduce duplication * Add tests for aws auth explicit wildcard constraints * Remove implicit prefix matching from AWS auth backend In the aws auth backend, bound_iam_role_arn and bound_iam_instance_profile_arn were ALWAYS prefix matched, and there was no way to opt out of this implicit prefix matching. This now makes the implicit prefix matching an explicit opt-in feature by requiring users to specify a * at the end of an ARN if they want the prefix matching.		2018-03-17 21:24:49 -04:00
..
audit	Add context to the NewSalt function (#4102)	2018-03-08 11:21:11 -08:00
credential	Allow non-prefix-matched IAM role and instance profile ARNs in AWS auth backend (#4071)	2018-03-17 21:24:49 -04:00
logical	Honor mount-tuned ttl/max ttl for database credential generatoin (#4053)	2018-03-15 09:24:02 -07:00
plugin	Remove logical.Initialize() method (#3848)	2018-01-25 20:19:27 -05:00