publish to azure via "mvn azure-functions:deploy" doesn't support service principal about azure-maven-plugins HOT 8 CLOSED

Hi @danyongliu

Currently Azure CLi login through service principal is not supported yet. For a work around, you can set the service principal in the Maven's setting.xml.

Check this for more details: https://github.com/Microsoft/azure-maven-plugins/blob/master/docs/common-configuration.md#authentication-method-1-use-the-maven-settingsxml-file

from azure-maven-plugins.

Related issue: Azure/azure-libraries-for-java#417

from azure-maven-plugins.

I still see an issue even with settings.xml

What did you pass in plugin configuration ? I am passing below

from azure-maven-plugins.

Hi! Is this still being worked on? We need this for our build pipelines.

from azure-maven-plugins.

Sorry for the delay
@sohelsyed In plugin configuration, we need to pass the authentication profile id and save the client/tenant/key into maven settings.xml, here is an example.

• settings.xml

  <servers>
    <server>
      <id>verify</id>
      <configuration>
        <client>${CLIENT ID}</client>
        <tenant>${TENANT ID}</tenant>
        <key>${KEY}</key>
        <environment>AZURE</environment>
      </configuration>
    </server>
  </servers>

• maven plugin configuration

<plugin>
        <groupId>com.microsoft.azure</groupId>
        <artifactId>azure-webapp-maven-plugin</artifactId>
        <version>1.6.0</version>
        <configuration>
          <authentication>
            <serverId>verify</serverId>
          </authentication>
          ...

@javisst Yes, we are still looking for solutions for this issue, before this, please set the service principal in maven's setting file as a workaround.

from azure-maven-plugins.

Hi @Flanker32 ,
I have verified this issue today, it still reproduces on Mac OS, here is my repro steps.
1. Run: az login --service-principal -u <app-url> -p <password-or-cert> --tenant <tenant> on bash.

2.Run: mvn azure-webapp:deploy.

My azure-cli version is 2.0.67, it works well on Windows.

from azure-maven-plugins.

The reason is because some of the caches in the log have not been cleared, and re-generation after clear will solve the problem.

from azure-maven-plugins.

This was caused by an issue of autorest-clientruntime-for-java and has been fixed in webapp plugin 1.7.0 and function plugin 1.3.3

from azure-maven-plugins.