users enter a portal URL, they are being passed to authenticate (in our AzureAD tenant) and always dropped on /web/guest/home.

[ryanbenedetti]

When users enter a portal URL, they are being passed to authenticate (in our AzureAD tenant) and are then always dropped on /web/guest/home. For example, when the user is not logged in and goes to the URL (https://myexampleliferay.up.edu/registrar/home) they are being redirected to login, and then passed to the Liferay default login page (i.e. /web/guest/home) rather than on /registrar/home.

We are using a Microsoft AzureAD tenant as our Identity Provider. We are also using the OpenID Connect plugin (https://web.liferay.com/marketplace/-/mp/application/78695724).

Somewhere along the authentication path the portal URL information is being dropped. This is a critical issue as we are T-minus 3 days to launch our new Liferay DXP portal to campus.

[gvanderploeg]

@rambocloack can you please tune your OoO autoreply so that you don't pollute Github issues? Thanks.

[gvanderploeg]

The oidc-plugin does not mingle with the original portal url, so I think the problem lies elsewhere.
Review your setting of the portal properties auth.forward.by.last.path, auth.forward.by.redirect and their counterparts in the UI in the control panel -> Instance Settings?