You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I dont know if this is a feature or a bug. I have frontend users setup with username and password. Then I have a frontend login page, where users can login to their fe users. This works fine.
As soon as I install the extension "mksamlauth" this does not work anymore. I do not create a configuration record for "SAML configuration", I just install the extension, and then "normal" frontend login does not work anymore.
I understand, that the extension provides functionality to login users depending on their SAML status, but I find it very strange, that event without configuration, the normal fe login process does not work anymore.
The text was updated successfully, but these errors were encountered:
hoermannklaus
changed the title
After installation default FE Login does not work anymore
After installation only default FE Login does not work anymore
Jan 20, 2020
This changed when the check for login-status was removed: c939f1c
@Baachi How was this planned to work? The login is now mandatory and you can't provide pages accessible without login or with separate login-methods under the same domain anymore? For other domains it should still work since the IdentityProviderRepository could not return a configuration (findByHostname), right?
I dont know if this is a feature or a bug. I have frontend users setup with username and password. Then I have a frontend login page, where users can login to their fe users. This works fine.
As soon as I install the extension "mksamlauth" this does not work anymore. I do not create a configuration record for "SAML configuration", I just install the extension, and then "normal" frontend login does not work anymore.
I understand, that the extension provides functionality to login users depending on their SAML status, but I find it very strange, that event without configuration, the normal fe login process does not work anymore.
The text was updated successfully, but these errors were encountered: