Disabled local authentication strategy is set to enable following conversion to V7

[RBourgeoisGH]

Description

When we have a local authentication strategy setup in V6 and we update the platform to V7, the local strategy is created enabled in the UI instead of using the value from the environment variable (you would need to manually disable in the UI in order to make it disappear).

The expected result should be:

• if we have a working SSO authentication setup and we are Entreprise Edition/Trial, we set up the local disabled or enabled according to the value of the env variable
• if we have don't have a working SSO authentication or we have a community edition, the local should be enabled upon conversion regardless of its value in the env variable

Workaround: login as admin on OpenCTI platform (with access to security > Authentication) and edit local strategy configuration to disable it.

[aHenryJard]

There is actually 2 issues:

• for an existing platform in 6.9.x, with local auth disabled => conversion set it to enabled, probably because it's config { disabled: true } and code looks for enabled here

  opencti/opencti-platform/opencti-graphql/src/modules/authenticationProvider/authenticationProvider-migration.ts

  Line 71 in 901f1ce

  await updateLocalAuth(context, user, settings.id, { enabled: local?.enabled ?? true });

• for a new platform on 7.x but configured with env var for local auth => it's totally ignored because of initial data initialization here

  opencti/opencti-platform/opencti-graphql/src/database/data-initialization.js

  Line 453 in 901f1ce

  local_auth: { enabled: true },

[aHenryJard]

For a new platform in 7.x it's ignored in purpose, since env var are deprecated. So only the first use case should be fixed (and only for EE platform, CE will have local enabled)

opencti/opencti-platform/opencti-graphql/src/modules/authenticationProvider/authenticationProvider-migration.ts

Line 71 in 901f1ce

await updateLocalAuth(context, user, settings.id, { enabled: local?.enabled ?? true });