v0.4.31

2018-05-17 Version 0.4.31

Features

• Improve MSI for VM token polling algorithm

v0.4.30

2018-05-16 Version 0.4.30

Features

• Allow ADAL 0.5.0 to 2.0.0 excluded as valid ADAL dependency

v0.4.29

2018-04-30 Version 0.4.29

Bugfixes

• Fix refresh Token on AADTokenCredentials (was broken in 0.4.27)
• Now UserPasswordCredentials correctly uses the refreshToken, and not user/password to refresh the session (was broken in 0.4.27)
• Bring back keyring, with minimal dependency 12.0.2 that fixes the installation problem on old Python

v0.4.28

2018-04-23 Version 0.4.28

Disclaimer

Do to some stability issues with "keyring" dependency that highly change from one system to another,
this package is no longer a dependency of "msrestazure".
If you were using the secured token cache of ServicePrincipalCredentials and UserPassCredentials,
the feature is still available, but you need to install manually "keyring". The functionnality will activate automatically.

v0.4.27

2018-04-18 Version 0.4.27

Features

• Implements new features of msrest 0.4.28 on session improvement. See msrest ChangeLog for details.

Update msrest dependency to 0.4.28

v0.4.26

2018-04-17 Version 0.4.26

Bugfixes

• IMDS/MSI: Retry on more error codes (#87)
• IMDS/MSI: fix a boundary case on timeout (#86)

v0.4.25

2018-03-29 Version 0.4.25

Features

• MSIAuthentication now uses IMDS endpoint if available
• MSIAuthentication can be used in any environment that defines MSI_ENDPOINT env variable

v0.4.24

2018-03-26 Version 0.4.24

Bugfix

• Fix parse_resource_id() tool to be case-insensitive to keywords when matching #81
• Add missing baseclass init call for AdalAuthentication #82

v0.4.23

2018-03-19 Version 0.4.23

Bugfix

• Fix LRO result if POST uses AsyncOperation header (Autorest.Python 3.0 only) #79

v0.4.22

2018-02-27 Version 0.4.22

Bugfix

• Remove a possible infinite loop with MSIAuthentication #77

Disclaimer

From this version, MSIAuthentication will fail instantly if you try to get MSI token
from a VM where the extension is not installed, or not yet ready.
You need to do your own retry mechanism if you think the extension is provisioning and
the call might succeed later.
This behavior is consistent with other Azure SDK implementation of MSI scenarios.