Liferay Login error in liferay DXP after migration - liferay-7

After logging in with my custom login portlet into liferay portal,it again redirects to another login with an error in console
"Ignoring login attempt because the password parameter was found for the request with the referer header":
Everything is fine after second login
How to resolve this?

Related

grafana can’t login after upgrading to v7.0

After upgrading to v7.0 we are unable to login to grafana. At the login screen, after typing in a the username and password, a green banner will pop up which states “Logged In”, but the webpage will refresh and be stuck at the login page.
Try using another browser. Google and Firefox works for me while Microsoft edge does not.

Configuring Liferay 7.2 OpenID Connect for Keycloak?

I have a fresh Liferay 7.2 and Keycloak 7 install
I created a Keycloak Client for Liferay
I enable Openid Connect in Liferay
In Liferay I configure an OpenID Connect provider with the Keycloak OpenID Connect discovery endpoint
In Liferay
I click Login, Login is presented
I click OpenID Connect, OpenID Connect Login page is presented
I click Login with the Keycloak provider selected, the browser is redirected to the Keycloak log in page
I enter my user and password and Click log in
My browser is redirected back to Liferay
In the Liferay the console looks like this https://gist.github.com/smitopher/ca8bcb2ccb564eff3a42a1944e8daed7
and the browser shows a Liferay Internal Server Error message
Any suggestions?
Some further debugging shows that When Liferay calls the Keycloak token endpoint, Keycloak returns a 400 http status and an invalid grant message.
I ran into the same problem but later stumbled across a blog post showing a successful configuration which I've reproduced with Liferay 7.2 + Keycloak 4.8.
The key difference between the failures and successes appears to be skipping auto-discovery and instead to populate the individual settings directly. It would appear that Liferay doesn't like something in Keycloaks discovery endpoint.
I recommend updating the Keycloak version and checking the correct Liferay configuration by consulting the official Liferay documentation Authenticating with OpenID Connect. You can also consult the article How to connect Keycloak and Liferay via OpenID Connect
Remember that Keycloak and Liferay must be able to communicate with each other via the HTTP / HTTPS protocol.

Moodle Authentication (auth_googleoauth2) plugin not working

i am using moodle 3.0.
I want to login with on my website, so i have downloaded Authentication (auth_googleoauth2) plugin from moodle directories.
also put the clientID and client secret into setting plugine page.
But on login page still not showing buttons for "login with google".
Any thing i am missing can any one help how to use this plugin.
Is it enabled? Go to site admin -> plugins -> authentication -> manage authentication
https://docs.moodle.org/30/en/Managing_authentication#Setting_the_authentication_method.28s.29

JAAS authentication in jboss 7 using customloginmodule (DatabaseServerLoginModule)

I am trying to do authentication in spring mvc application using picketlink with jboss 7.
I have configured web.xml,jboss-web.xml,standalone.xml for custom login module,
picketlink-idfed.xml,picketlink-handlers.xml.
I have my customlogin module which extends Databaseserverloginmodule.
When I try to login I am getting blank page as 404 error and my customlogin module is not called as authentication is not happening.
Am i missing any configuration?
Any help would be appreciated

Customising Web-logics default 404 error page

I am running weblogic 9. When I enter an incorrect URL below the application root I redirect 404 request to a customized error page.
Eg. http://localhost:7001/myApp/non-existent redirects to my customised error page.
Is there a way to do this for all incorrect URLs entered, not necessarily below the application root?
Eg. http://localhost:7001/anything_non-existent should redirect to my customized error page, not the web-logic default one?
Thanks
The application's web.xml is where you define the error-page for <error-code>404</error-code>
http://localhost:7001/anything_non-existent is actually looking for a missing web application.
If you have a web server like Apache in front of Weblogic, that is the right place to trap this and redirect to 404.