Conversation
|
✅ Work item link check complete. Description contains link AB#3525780 to an Azure Boards work item. |
|
❌ Work item link check failed. Description contains AB#3525780 but the Bot could not link it to an Azure Boards work item. Click here to learn more. |
|
✅ Work item link check complete. Description contains link AB#3525780 to an Azure Boards work item. |
1 similar comment
|
✅ Work item link check complete. Description contains link AB#3525780 to an Azure Boards work item. |
There was a problem hiding this comment.
Pull request overview
Updates documentation in AuthenticationSettings#setSecretKey to more accurately describe the impact of supplying a custom key on previously encrypted data.
Changes:
- Refines the Javadoc warning about unreadable previously encrypted content when a user-provided key is involved.
| * this method must be invoked before any other MSAL classes, | ||
| * otherwise the key might not be loaded | ||
| * (The existing encrypted key will not be readable, | ||
| * (The existing data (that was encrypted by the user provided key) will not be readable, |
There was a problem hiding this comment.
Doc grammar/clarity: “user provided key” should be “user-provided key”, and the nested parentheses make the sentence harder to read. Consider rewriting as a single parenthetical (e.g., ‘Existing data encrypted with a user‑provided key…’).
AB#3525780