Create User, Create group and Tenant option are not visible on Admin Dash board

I have created spring boot and deployed on Azure cloud as docker container.

When i run the application in local i can able to access Create New user, tenant and Group. But same thing if deployed on cloud i am not getting option.

And One more Observation when I make call with Method OPTIONS
camunda/api/engine/engine/default/user/

I am getting 204. But in local i am getting 200 with all available method.

I am thinking this might be issue.

@Niall Could you please help me on this issue?

@shashikumar_shivanna you need to enable cors filter for Access-Control-Allow-Origin.

@Configuration
public class CORSFilterConfig {

  @Bean
  public CorsFilter corsFilter() {
    UrlBasedCorsConfigurationSource corsConfigurationSource = new UrlBasedCorsConfigurationSource();
    CorsConfiguration corsConfiguration = new CorsConfiguration();
    corsConfiguration.setAllowCredentials(true);
    corsConfiguration.addAllowedHeader("*");
    corsConfiguration.addAllowedOrigin("*");
    corsConfiguration.addAllowedMethod(HttpMethod.GET);
    corsConfiguration.addAllowedMethod(HttpMethod.POST);
    corsConfiguration.addAllowedMethod(HttpMethod.OPTIONS);
    corsConfiguration.addAllowedMethod(HttpMethod.PATCH);
    corsConfiguration.addAllowedMethod(HttpMethod.PUT);
    corsConfiguration.addAllowedMethod(HttpMethod.HEAD);
    corsConfiguration.addAllowedMethod(HttpMethod.DELETE);
    corsConfigurationSource.registerCorsConfiguration("/**", corsConfiguration);
    return new CorsFilter(corsConfigurationSource);
  }
}

@aravindhrs Thanks you, Let me check

@aravindhrs Still i am facing issue after adding this config.

Is it cluster setup?

@aravindhrs No its not cluster setup

There might be a few things you might want to check.

  • Do you have ADMIN privileges for those credentials you use? [-> add user in you bpm-platform.xml file or give it access to the module you want through the ADMIN saccount]
  • I do not know much about Azure but based on other Cloud providers, verify if Azure Network Security Groups (just looked that up) allow traffic on the ports you need them to.
    Cheers

Got the solution it was issue with nigix annotation

Glad you could find a solution.