Ask Questions and Find Answers

Hi Florian,

Could you please describe how you solved it with a private page?

Thanks,
Zsigmond

When you don't have a public page you are redirected on Open Id Provider Page.

And adding this property :
auth.login.url=/home/-/login/openid_connect_request?p_p_state=maximized&_com_liferay_login_web_portlet_LoginPortlet_saveLastPath=false&_com_liferay_login_web_portlet_LoginPortlet_redirect=/&_com_liferay_login_web_portlet_LoginPortlet_OPEN_ID_CONNECT_PROVIDER_NAME=OpenId

Change OpenId by OpenId configuration provider name

​​​​​​​

Hi Florian,

Then I guess you want the users to be redirected to there in each case when they hit a restricted resource, right?

If so, why doesn't it work now, without the private pages?

I need more details to understand the real problem. Could you please describe the whole use case?

Thanks.
Zsigmond

Hello Zsigmond,

Without the private pages feature when accessing the site we are redirected to the liferay authentication screen.

When clicking on the sign in button we are redirected to the provider open id authentication with the auth.login.url set to the OpenId configuration (https://help.liferay.com/hc/en-us/articles/4407989179661-How-to-Redirect-to-OpenID-Connect-Page-after-clicking-the-Sign-In-Button). Otherwise the user is redirected to the login portlet with the possibility to authenticate via login password or to select a Provider Open Id.

The need is when accessing the site if the user is not logged in and the open id is enabled, to have the possibility to redirect the user directly to the provider authentication url. As mod_auth_openidc would do on an apache for OpenId authentication.

Best Regards,

Florian

Hi Florian,

What is the target when you access the site? Is that a regular page? If so, have you configured the page already so that it needs authentication to access?

Regards,
Zsigmond