http-kernel | Provides a structured process for converting a Request | Web Framework library

That composer.json file is a bit of a mess. Some Symfony packages on 5.3, some even on 5.1, and many on 6.

Also you are controlling Symfony versioning from extra.symfony.require, and at the same time from the discrete version constraints. You include some packages that no longer exist on 6.0 (symfony/security-guard), and are missing some that should be installed on a 6.0 version.

It's simply not on an installable state.

I've managed to make it installable changing it like this:

Ok, now im deprecation free but there are some things to now after upgrading from 4.4 to 5.3

To find all warnings I created a new symfony project to compare different files

1. KernelEvent::isMasterRequest()" is deprecated, use "isMainRequest()

   take a look into your file src/Kernel.php - there u can find the deprecated method

2. The "session.storage.factory.service" service is deprecated

   open your framework.yaml and compare with the following code. Maybe it could help you:

Please have a look at the documentation of Composer scripts. It explains pretty obvious:

post-install-cmd: occurs after the install command has been executed with a lock file present.

If you are using composer install with a lock file not present (as indicated from the console output), this event is not fired.

Your domain is not being recognized as a GitLab domain, and then the package is simply cloned out of the Git repository.

You should configure your domain as being a GitLab domain so Composer knows to use the Gtlab API.

Unless you configure other domains, only gitlab.com is considered a GitLab domain.

https://getcomposer.org/doc/06-config.md#gitlab-domains

The configuration should go within config.gitlab-domains, as far as I can see. Something like

I was able to solve the issue on my side by renaming the config files from .yml to .yaml.

So my /config folder now looks like this:

I also had to change the imports in the environment specific configs under config/packages/$ENV/*.yaml to this (note the ../../):

Looks like a URL issue. Did you check the URL you are invoking? As per the documentation in the link you have shared :

"port 443 inside the Webapp container is mapped to the port 32477 on the Kubernetes cluster.

You need to use https://your-minikube-cluster-ip:your-webapp-service-targetport (e.g., https://10.101.114.46:32477) as the API root URL when using the Postman collection."

But as per your logs, I see the port number used is 31599. https://192.168.88.80:31599/auth/v1/login/

Regards, Prince Arora

I manage to fix my problems... I don't know if somenone else could be interrested in the solution but just in case...

• Problem 1 : normalization groups doesn't work :

By writing

Did you install symfony/apache-pack. It allows you to access any URL on your application without having to include /index.php in the path.

In order to quickly enable rewriting for the Apache web server, you can install the symfony/apache-pack recipe, which places a suitable .htaccess file into your public/ directory:

Like I said in my answer to the comment of Patrickkenekayoro, I forgot a change in the User entity: The getUserIdentifier() function should bring back the username, instead of the email.