Portal user is redirected to PortalMainPageModule when following direct link

Hello,

Hope you're doing well.

If I understood your question correctly, it seems there is some issues with permissions, on this demand we would like to suggest you update Organizational and Functional roles, Object permissions as well to apply the latest changes.

Regards,

Roman

Roman Rak,

thank you for your unswer. We did all that, but the issue wasn't resolved. This seems line an issue with routing. Can you help with which js module is responcible for routing? So we can try to debug this. 

Thanks!

Юлія Дяків,

Thanks for your prompt response.

It's still a bit unclear what you mean under "when portal user follows direct link to record that has no section". Could you please provide us with screenshots or with a recording of the issue reproduction? If it's not possible, please contact us via email (support@creatio.com) so we will be able to review your request with more details.

Regards,

Roman

Roman Rak,

when I say "when portal user follows direct link to record that has no section" I mean that this linl is link to edit page of detail records. So we have section for Entity1, open edit page1 from there. And inside of the page1 there is detail with list of connected records - Entity2, when we open some record from detail we open edit page2. There is no section for Entity2, only detail. But we can construct direct link to Edit page2 and give it to user. When licence user follows it all works correctly - edit page 2 is opened. But when portal user opens it - he is redirected to PortalMainPageModule.

Does this clarify a bit the problem? 

Regards, Iuliia

Hello Юлія,

Thank you for rephrasing the issue description.

At first, in case you are on the record page (let it be Activity page) trying to open the record from the detail on that page (let it be related to Account record), the link in the address bar is not being changed, so if you copy this URL and pass it to the portal user who doesn't have access to the Activity section, the behavior will be the same — user will be redirected to the home portal page. So in case, you want to provide the link for the Account detail record, you will need to open this detail record in a new tab/window, after that there will be available the proper link (this is OOTB logic and for now can not be changed, but we already have created a functional request for our developers on this topic).

Also if you shared the proper link to the needed record and the portal user still faces the same issue, please check access settings exactly for this record (at least there should be added this portal user or all needed portal users, user roles), because it looks like that user doesn't have the appropriate access to that record or section in general (we have tested, and it looked exactly how you described the issue).

Regards,

Roman

Roman Rak,

thanks for taking time to explain all those details.

But the case is that user has all rights that he needs to see this record. Portal user can see data in record Activity when he follows Activity Section => Activity page => Account detail => Account page (taken as example from your explanation)  but when opening direct link to Account page he is redirected to  PortalMainPageModule. (in our system Account object from example does not have section, only detail. We think this is important detail because when portal user follows direct link to some page that has section - no issue reproduced. )

 The link itself is correct and leads to correct edit page for licence users.

I was able to record video of described behaviour, but unfortunatelly can't attach gif file here.

As there is no error in console, we can't debug this issue, to find the cause. So we need some hint what part of routing behaviour to check for issues. 

Thanks.

Hi, I have the same issue. This PORTAL user has the all access rights and in v.7.14 can open url. But after update to v.7.18.3 - redirect to Main Page. Why? Do you have some ideas?

Hello,

If the issue appeared after the upgrade to the latest version, we suggest checking upgrade logs as far there could appear some issues that affected the access rights. Also, the website can be restarted and re-licensed, after that please flush Redis and check all the needed updated licenses.

Regards,

Roman