use_mtls_endpoint_aliases name
Why is the name use_mtls_endpoint_aliases? In particular, what are the “aliases” that are being referred to? This isn’t clear from the specification.
Wouldn’t a better name be something like “mtls_use_preferred” or “mtls_use_requred”, depending upon the intent?
Comments (5)
-
reporter -
reporter - changed component to FAPI2: Security Profile
- changed milestone to FINAL
-
reporter We discussed - doesn’t need to block public revview process. But we do need to address it.
From the call, there is reluctance to change the name as it has already been used in implementations. However perhaps the text could be made clearer.
-
I agree the text could change.
But the name is accurate, even more so once what “aliases” refers to in the decription gets clearer.
And the suggested names aren’t good enough. This metadata means to particularly solve the aliases use issue, it should have aliases somewhere in the name.
-
I mistakenly said on the call that the email was not public. But it is and this is the thread https://mailarchive.ietf.org/arch/msg/oauth-ext-review/9yd0R6hVAKLrD3UOMvvWuj9Aqwk/
- Log in to comment
posted a message from an email chat with a query about the metadata name