)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"0f8aa2320de5a285f4af32dbf20a6a7e83e8ed94","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Add new config option and setup for token keys"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"This change adds new configuration options under the `token`"},{"line_number":10,"context_line":"section for key_repository and max_active_keys. These settings"},{"line_number":11,"context_line":"are meant to replace the settings of the same name under the"},{"line_number":12,"context_line":"`fernet_tokens` catagory, which this change also deprecates."},{"line_number":13,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"9f6a8fd7_2a6b19b7","line":10,"updated":"2018-04-23 15:41:27.000000000","message":"After thinking about this, is there ever a case where we want to have both of these bits defined for each provider? Hypothetically speaking, if we had a JWT token provider and Ferent token provider, and someone wanted to switch from one to the other, would it make it easier to supply both at the same time?\n\nThis is probably building on a lot of assumptions, but if someone wanted to provide a smooth migration [0] from one to the other, they might need to know the location of both.\n\n[0] https://www.lbragstad.com/blog/migrating-token-formats-without-downtime","commit_id":"1909555e727b1d82e770ac5a6c402adb632529dd"},{"author":{"_account_id":21420,"name":"Gage Hugo","email":"gagehugo@gmail.com","username":"ghugo"},"change_message_id":"54029f1b84d97d5defa9d8b82fd08a989a21e939","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Add new config option and setup for token keys"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"This change adds new configuration options under the `token`"},{"line_number":10,"context_line":"section for key_repository and max_active_keys. These settings"},{"line_number":11,"context_line":"are meant to replace the settings of the same name under the"},{"line_number":12,"context_line":"`fernet_tokens` catagory, which this change also deprecates."},{"line_number":13,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"9f6a8fd7_2f66c1c2","line":10,"in_reply_to":"9f6a8fd7_2a6b19b7","updated":"2018-04-23 22:32:34.000000000","message":"From your \u0027hybrid_provider\u0027 I can see that use case. They would indeed need to have both locations defined so this wouldn\u0027t work then.\n\nI\u0027m wondering if we don\u0027t use this, then we may need to duplicate some of the fernet implementation then if we support that route.","commit_id":"1909555e727b1d82e770ac5a6c402adb632529dd"}]}