- Switch to the v1.0 REST endpoint.
- Updated to use the new Graph API calls for managing app passwords. Call the
az_app$add_password()
method to add a password to an app, andaz_app$remove_password()
to remove it. As a security measure, app passwords can no longer be manually specified; instead all passwords are now auto-generated on the server with a cryptographically secure PRNG.- The
az_app$update_password()
method is defunct.
- The
- Better handling of app creation with certificates:
- The
certificate
argument toms_graph$create_app()
can be the name of a .pfx or .pem file, anopenssl::cert
object, anAzureKeyVault::stored_cert
object, or a raw or character vector containing the certificate. - New
az_app$add_certificate()
andaz_app$remove_certificate()
methods, matchingadd_password
andremove_password
.
- The
- Treat the access token as opaque; this prevents errors when logging in without an AAD tenant.
- Fix a bug in user methods for listing objects when the result is empty.
- Fix a bug in retrieving users added to an Azure Active Directory (AAD) tenant from an external directory.
- Allow AAD v2.0 tokens to be used for authenticating. Note that AAD v1.0 is still the default and recommended version.
- Use
utils::askYesNo
for confirmation prompts on R >= 3.5, eg when deleting objects; this fixes a bug in reading the input. As a side-effect, Windows users who are using RGUI.exe will see a popup dialog box instead of a message in the terminal. - Various other bug fixes.
- Improved handling of null object properties.
- Changes to login functionality to better accommodate AzureAuth options. As part of this, the
config_file
argument foraz_graph$new
has been removed; to use a configuration file, call the (recommended)create_graph_login
function.
- Fix some bugs in the login functionality.
- Add direct support for creating apps with certificate credentials.
- Submitted to CRAN