Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
RE: Login off to an external URL LF7
Is their away through to configuration to have liferay redirect to an external IP address. I'm using keycloak with Liferay which works great for SSO but when my session timeout I'm going to my Liferay login page. I was trying to use the default.logout.page.path property to take me to my site path which I was hoping the trigger another Keycloak login but it didn't seem to work.
I was going to try creating a sign out page that redirects to an external url and then set the default.logout.page.path property to it. Is they an easier or better way to handle this?
I was going to try creating a sign out page that redirects to an external url and then set the default.logout.page.path property to it. Is they an easier or better way to handle this?
Hmm, I've used the default logout to redirect to external page, so it should work for you too, William. What version are we talking about?
<p>I always thought that default logout had to be a relative page in liferay. You were able to give a full url?</p>
I'm using 7.2 DXP GA 1, I just set my default logout url to https://www.google.com and saved it and it worked fine.
Yeah I just tested that as well. I always thought this had to be a relative page. After 9 years of doing Liferay I'm still leaning things. Thanks again.
One thing I also learned is that the setting for the default logout url could only be made from inside the control panel's instance settings page. Apparently once this setting in portal-ext.properties file is loaded the first time it can no longer be changed through the properties file. It must be change in the control panel to take affect. I'm not sure if I really like this behavior or not. This holds true the home and landing pages as well. Once I knew this I was able to solve my original issue of redirecting to my keycloak login page. I could even cause this to happen by reference my relative base path, /web/<my site path>. This was intercepted by the OpenId Connect plugin that I'm using which then redirected my back to keycloak.
There are some properties that are only used at first launch; afterwards the control panel is the only way to affect change.
Mostly these fall into "cluster-wide" settings like this one, the main site name, the admin user email, screenname, etc.
Node-specific settings like whether it should enforce https, the module framework properties, etc. those will continue to come from portal-ext.properties.
Mostly these fall into "cluster-wide" settings like this one, the main site name, the admin user email, screenname, etc.
Node-specific settings like whether it should enforce https, the module framework properties, etc. those will continue to come from portal-ext.properties.
Thanks David for this clarification. Its much appreciated.
Copyright © 2025 Liferay, Inc
• Privacy Policy
Powered by Liferay™