You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering if the root cause of #1953 was incorrectly diagnosed, or if maybe Azure have changed their API again. If i peg my azurerm provider version to = 1.15 (i.e. the latest release before the "fix" in #1960 was merged) I can apply the following template without problems:
provider "azurerm" {
version = "= 1.15"
}
resource "azurerm_azuread_application" "ad_app" {
name = "tomas-testing"
}
In other words, I cannot reproduce the original issue (#1953).
However, as of #1960 and version 1.16, no URLs on the application can be http, which disallows something like this:
Again, this template applies successfully with 1.15 but fails on 1.16. This effectively makes impossible to e.g. set reply urls for AzureAD applications that enable local testing of OAuth flows (without configuring your local development environment to run https).
Is there any chance #1960 could be reverted for the next release, to re-enable this configuration?
PS. This template, touching all three types of URLs and setting them to HTTP-schemed values, also works without problems on 1.15:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!
ghost
locked and limited conversation to collaborators
Mar 5, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi!
I'm wondering if the root cause of #1953 was incorrectly diagnosed, or if maybe Azure have changed their API again. If i peg my
azurerm
provider version to= 1.15
(i.e. the latest release before the "fix" in #1960 was merged) I can apply the following template without problems:In other words, I cannot reproduce the original issue (#1953).
However, as of #1960 and version
1.16
, no URLs on the application can behttp
, which disallows something like this:Again, this template applies successfully with 1.15 but fails on 1.16. This effectively makes impossible to e.g. set reply urls for AzureAD applications that enable local testing of OAuth flows (without configuring your local development environment to run https).
Is there any chance #1960 could be reverted for the next release, to re-enable this configuration?
PS. This template, touching all three types of URLs and setting them to HTTP-schemed values, also works without problems on 1.15:
The text was updated successfully, but these errors were encountered: