• Bugfix to address error "InvalidScope : FaultMessage: ID3082: The request scope is not valid or is unsupported." when using username-password flow with federated user account while your tenant is migrating to a different cloud. (#240)

• Update project metadata on PyPI (#231 )

• Enabled dynamic whitelisting of dSTS endpoints (#215 )
• World wide authority updated from login.windows.net to login.microsoftonline.com (#227 )

• Adjust the public cert input to accept a pem-format content with or without those -----BEGIN CERTIFICATE----- tag lines. (#199, #207)
• Change the default logging level from INFO to DEBUG (#197, #200, #122). There is also a canonical way to customize python logging, documented in our wiki now.

• Enhancement: Added support for WSS SAML1.1 and 2 token types (#186, #187 )
• Updated requirements.txt to pick up the vulnerability fix included in requests 2.20.0 (#179 )

• Enhancement: Added support for Subject Name / Issuer authentication (#173)

• Enhancement: Added whitelisted domains for dSTS (#164)

• Fixes incorrect cache operation in authorization code flow (#161). The issue was observed in previous version 0.6.0, 0.7.0, 1.0.0, 1.0.1.

• Relaxed authority url check (#156,#157)
• We discovered and fixed an incorrect cache behavior in 0.6.0, 0.7.0, 1.0.0, 1.0.1. Please upgrade to 1.0.2 or later.

• This release includes a breaking change which we have planned for more than 1 year. The default value of api_version parameter in the AuthenticationContext constructor has been changed from "1.0" to None. You can still explicitly set it to "1.0" to maintain the old behavior, if needed. (See details in #137)
• This release is otherwise exactly the same as 0.7.0. If you do not want this new behavior, you can pin your environment with 0.7.0. Going forward, new development will happen in 1.x series.
• We discovered and fixed an incorrect cache behavior in 0.6.0, 0.7.0, 1.0.0, 1.0.1. Please upgrade to 1.0.2 or later.

• Enhancement: Added authorization code flow support for public clients (#149)
• Enhancement: Added Proof Key for Code Exchange (PKCE) support in authorization code flow for public clients (#150)
• Enhancement: Raises a value error when the authority url is not in the expected format (#126, #151)
• We discovered and fixed an incorrect cache behavior in 0.6.0, 0.7.0, 1.0.0, 1.0.1. Please upgrade to 1.0.2 or later.

• Enhancement: Added token cache support for auth code flow (#138 )
• Enhancement: Added parameters to AuthenticationContext to support ssl verification and proxies (#142 )
• We discovered and fixed an incorrect cache behavior in 0.6.0, 0.7.0, 1.0.0, 1.0.1. Please upgrade to 1.0.2 or later.

• Enhancement: Add a new parameter in the AuthenticationContext to turn on Personally Identifiable Information (PII) in logs. (#124)
• Enhancement: Acquiring token via WSTrust will also have timeout behavior now. (#121, #125)
• Bugfix: Previously ADAL Python had some issue when the Azure AD tenant is federated with an on-prem AD. Now fixed. (#80, #120)
• Enhancement: Handle rare multithread racing issue observed when using profiler (#123, #128)

• Enhancement: Add a new parameter in the AuthenticationContext to pass requests (connect,read) timeout parameters. (#112)
• Adjustment: By default, no Personally Identifiable Information (PII) will be logged by ADAL Python. (#111)
• Adjustment: Surfaces the requests.HTTPError so that app developer can deal with the Retry-After info from HTTP 429 error, if desired. (#117)

Bugfix: Handle refresh token in Azure Stack (ADFS 2016) properly (#105)

• Enhancement: Add one more trusted authority host login.microsoftonline.us (#77, #78)
• Enhancement: Bubble up the server response. (#85, #88)
• Bugfix: Should not attempt to refresh a token when RT is unavailable (#82, #87)
• Bugfix: Now we force utf-8 decoding so that package builders would be able to pack ADAL Python regardless of their locale. The ADAL Python library users will NOT be affected by this change. (#89, #91)
• Other sample code and readme file adjustments (#76, #73, #84, #92, #95, #97, #98)

• Fixes platform resolution issue found in Gunicorn/Gevent context (#74)

• Revert a workaround introduced in 0.4.3, we now have better understanding and recommend a different way to solve it. (#61)

• Fixes logger bug to ensure proper logging (#55)
• Updates dependency to exclude the requests package 2.12.* (#58)
• Introduces a new switch to override the default behavior (#57)

• Fix decoding exception when decoding id_token with non-ASCII characters on Python 2.x (#52)
• Minor adjustment on version string handling (#48)

1. Fix encoding exceptions on formatting error text #44
2. Minor typo fixes in sample code #45

1. Support login using federated credentials through protocols of wstrust 1.3 or 2005
2. Support http tracing through proxies by exposing the environment variable of ADAL_PYTHON_SSL_NO_VERIFY

1. Support device code flow, required for accounts with 2FA enforced, or MSA accounts such as live id
2. Support service principal with certificate.
3. Support token cache.
4. Remove all JS style of callbacks for better code readability and maintainability.
5. Improve 'AuthenticationContext' class to be consistent with ADAL node and C# versions.
6. Add samples showing how to use the ADAL in correct ways. Convenient methods in init.py were removed as it has no integrations with cache and used client id belonging to other client app.
7. Update readme with common authentication flows and smooth package installations.
8. Update for US Government and German Government Authority.

Edit:

Note: Changes on 'client_id' and 'resource' arguments after 0.1.0

The convenient methods in 0.1.0 have been removed, and now your application should provide parameter values to client_id and resource.

2 Reasons:

• Each adal client should have an Application ID representing a valid application registered in a tenant. The old methods borrowed the client-id of azure-cli, which is never right. It is simple to register your application and get a client id. You can follow this article.

• The old method defaults the resource argument to 'https://management.core.windows.net/', now you can just supply this value explictly. Please note, there are lots of different azure resources you can acquire tokens through adal though, for example, the samples in the repository acquire for the 'graph' resource. Because it is not an appropriate assumption to be made at the library level, we removed the old defaults.