Not working too, but without composer require symfony/amazon-mailer.
I'm getting same error message

Any updates to this isssue?

I can confirm this does not work with me as well.
Running mautic-docker on 5.0.3.
Downgrading to 4.4.9 works as expected.
It is unfortunate that the community is being driven to 5.x without core features covered.

+1 SAML is not working.

Error:

[2024-03-21T22:17:01.775952+00:00] mautic.CRITICAL: Uncaught PHP Exception ArgumentCountError: "LightSaml\SpBundle\Controller\DefaultController::__construct(): Argument #1 ($metadataProfileBuilder) not passed" at /var/www/mautic/vendor/lightsaml/sp-bundle/src/LightSaml/SpBundle/Controller/DefaultController.php line 29 {"exception":"[object] (ArgumentCountError(code: 0): LightSaml\\SpBundle\\Controller\\DefaultController::__construct(): Argument #1 ($metadataProfileBuilder) not passed at /var/www/mautic/vendor/lightsaml/sp-bundle/src/LightSaml/SpBundle/Controller/DefaultController.php:29)"} {"hostname":"ip-10-0-2-135","pid":16264}

+1 SAML is not working

[2024-03-26T08:37:26.830272+00:00] mautic.CRITICAL: Uncaught PHP Exception ArgumentCountError: 
"LightSaml\SpBundle\Controller\DefaultController::__construct(): Argument #1 ($metadataProfileBuilder) not passed" at 
.../vendor/lightsaml/sp-bundle/src/LightSaml/SpBundle/Controller/DefaultController.php line 29 
{"exception":"[object] (ArgumentCountError(code: 0): LightSaml\\SpBundle\\Controller\\DefaultController::__construct(): 
Argument #1 ($metadataProfileBuilder) not passed at 
.../vendor/lightsaml/sp-bundle/src/LightSaml/SpBundle/Controller/DefaultController.php:29)"} {"hostname":"...","pid":3724925}

As a side effect, users are redirected to:
https:// mautic.your.domain /s/saml/login
where they receive a 500 Internal Server Error

Link to the standard (non SAML) login is:
https:// mautic.your.domain /s/login

@RCheesley you told @ #12304 (comment) that you are focused to mautic 5.x but it's as buggy as 4.4.x series 🤔

@RCheesley you told @ #12304 (comment) that you are focused to mautic 5.x but it's as buggy as 4.4.x series 🤔

While I have great respect for the efforts made to bring us mautic 5.x, I can't hide that I'm very scared of all those red bug icons on the first page of issues here...

+1 SAML does not work
I use SAML-based login with Entra (Azure AD). "Test this application" in Entra works! But not when browsing directly to site_url. Redirect to s/saml/login gets the 500 code, error messages appear in the logs as posted above.

I'm impatiently waiting for SAML to work...

We do know that it's frustrating, and we're holding up the 5.1 release to ensure that this is fixed. We just haven't got anyone who is able to work on this yet.

While at it pls consider adding OIDC.

While at it pls consider adding OIDC.

It's not on the plans right now, but if it's something you're interested in please do feel free to add some funds to the bounty pot which would mean we could fund a developer to work on it (see the info in the original post).

Hi folks! Thanks to @mollux we have a fix for this issue. Please can you review, test and report back on this PR: #13742

General instructions for testing: https://mau.tc/tester but please check the instructions in the PR for specific instructions (please especially do the bit about leaving your review!)

Thanks all!

Hey everyone, please test #13742 if you want to get this fixed in Mautic 5.1.0. Otherwise I'll release it without it.

Hi @escopecz, thanks for handling this issue, when is the deadline for version 5.1.0? I'm too busy today and tomorrow, I think I can try it on Wednesday. If it's too late, it doesn't matter, we will publish it in the next version :-)

Wednesday is OK. Thank you!

Hi, i applaied two changes in my files:

• Add missing service arguments to controller SpBundle#2
• Fix/saml integration #13742

But i follow getting error in DefaultController line 29:
mautic.CRITICAL: Uncaught PHP Exception ArgumentCountError: "LightSaml\SpBundle\Controller\DefaultController::__construct(): Argument #1 ($metadataProfileBuilder) not passed" at /var/www/html/mautic/vendor/lightsaml/sp-bundle/src/LightSaml/SpBundle/Controller/DefaultController.php line 29 {"exception":"[object] (ArgumentCountError(code: 0): LightSaml\SpBundle\Controller\DefaultController::__construct(): Argument #1 ($metadataProfileBuilder) not passed at /var/www/html/mautic/vendor/lightsaml/sp-bundle/src/LightSaml/SpBundle/Controller/DefaultController.php:29)"} {"hostname":"ironman","pid":1162}

@javiervalerocelada it's not only about updating files. The problem isn't in Mautic itself but in another library that Mautic depends on. Dependencies are handled with Composer. In order to update the dependencies you must let Composer do it's thing. #13742 is there only to showcase how to test it. It won't be merged. But look at step 1 in the steps to test.

Wednesday is OK. Thank you!

I tried to test the #13742 PR as per your instructions, but unfortunately I couldn't get past the first login screen. I'm not very familiar with Gitpod so I'm probably missing something here, but after configuring it and arriving at the Mautic login screen, when I try to login with admin/mautic I get this message:
Your password is too weak. Please reset it.

After following the reset procedure I see this new message:
A new password has been generated and will be emailed to you, if this user exists. If you do not receive it within a few minutes, check your spam box and/or contact the system administrator.

I thought I'd get the email on the GitHub user, but nothing gets there. No spam either. Sorry I have no idea how the admin email is configured in that Gipod istance and where the new password is sent. I'll try again in the weekend on a local server but it'll take a little bit more to setup the test enviroment.