unmark object ID or Name for formatting#29397
Conversation
0c249e6 to
8c68c7d
Compare
|
I'm not sure about this solution. Since the identifying attributes heuristic is out of the user's control, displaying a name/ID marked as sensitive seems dangerous to me. What if instead of this, we check if the identifying attribute value is sensitive, and ignore it if so? |
|
The first check here is |
|
Unless I'm misunderstanding, that will check if the containing object itself has the sensitive mark, but not the enclosed value (i.e. the name/ID string). |
|
Oh, you are correct! I had some refactoring I discarded and that check no longer makes sense. I'll drop sensitive values individually. |
8c68c7d to
8c08c30
Compare
8c08c30 to
a48b024
Compare
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
It's possible that an "identifying" attribute could have marks. Make sure we don't return sensitive values as identifying attributes, and unmark the entire value when converting to a string.
Fixes #29374