Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Identity] Changelog updates before releasing #11646

Merged
merged 4 commits into from
Oct 6, 2020

Conversation

sadasant
Copy link
Contributor

@sadasant sadasant commented Oct 5, 2020

Setting up the release date for Identity as Tomorrow just to give me some range of action.

I also added some changelog entries that were missing. Feedback appreciated! ✨

@sadasant sadasant self-assigned this Oct 5, 2020
@ghost ghost added the Azure.Identity label Oct 5, 2020
@@ -1,6 +1,6 @@
# Release History

## 1.2.0-beta.2 (Unreleased)
## 1.2.0-beta.2 (2020-10-05)

Copy link
Contributor Author

@sadasant sadasant Oct 5, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

David and I were talking about what could go to the release highlights from these changes. We've agreed on the first three items so far.

So, this would be in the release highlights:

  • DefaultAzureCredential now by default shows the Device Code message on the console. This can still be overwritten with a custom behavior by specifying a function as the third parameter, userPromptCallback.
  • Added support for multiple clouds on VisualStudioCodeCredential. Fixes customer issue 11452.
  • ManagedIdentityCredential has been aligned with other languages, now treating expected errors properly. This fixes customer issue 11451.
  • Added Active Directory Federation Services authority host support to the node credentials.

Thoughts?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added ADFS authority Host support to the node credentials.

Two updates on the CHANGELOG based on recent PRs.

- `DefaultAzureCredential` now by default shows the Device Code message on the console. This can still be overwritten with a custom behavior by specifying a function as the third parameter, `userPromptCallback`.
- Added support for multiple clouds on `VisualStudioCodeCredential`. Fixes customer issue [11452](https://github.com/Azure/azure-sdk-for-js/issues/11452).
- `ManagedIdentityCredential` has been aligned with other languages, now treating expected errors properly. This fixes customer issue [11451](https://github.com/Azure/azure-sdk-for-js/issues/11451).
- `InteractiveBrowserCredential` authentication now uses the silent flow if the user provides a cache and authentication record for lookup.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comes from: #11407

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is the only important change for now, since Jonathan is working on further improvements. I could have missed something though.


- `DefaultAzureCredential` now by default shows the Device Code message on the console. This can still be overwritten with a custom behavior by specifying a function as the third parameter, `userPromptCallback`.
- Added support for multiple clouds on `VisualStudioCodeCredential`. Fixes customer issue [11452](https://github.com/Azure/azure-sdk-for-js/issues/11452).
- `ManagedIdentityCredential` has been aligned with other languages, now treating expected errors properly. This fixes customer issue [11451](https://github.com/Azure/azure-sdk-for-js/issues/11451).
- `InteractiveBrowserCredential` authentication now uses the silent flow if the user provides a cache and authentication record for lookup.
- Added Active Directory Federation Services support. This behavior happens automatically, without user intervention.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comes from: #11591

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

adfs is Active Directory Federation Services, right?

@sadasant sadasant requested a review from g2vinay October 5, 2020 20:21
@sadasant
Copy link
Contributor Author

sadasant commented Oct 5, 2020

This also changed:

https://github.com/Azure/azure-sdk-for-js/pull/11453/files#diff-4ad1f555a3b7efd54e06e998e7ecdfc0R60-R64

But it's a very internal thing, and an additive change that won't break anybody's code. I wonder if we should not add it to the changelog.

@sadasant sadasant changed the title [Identity] Release date in the Identity changelog [Identity] Changelog updates before releasing. Oct 5, 2020
@sadasant sadasant changed the title [Identity] Changelog updates before releasing. [Identity] Changelog updates before releasing Oct 5, 2020
Copy link
Member

@g2vinay g2vinay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can also add, "Added ADFS Authority Host support to the node credentials." to the changelog.

@sadasant sadasant requested a review from g2vinay October 5, 2020 20:48
sadasant added a commit to Azure/azure-sdk that referenced this pull request Oct 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants