Ask Questions and Find Answers

Is the page that is being linked to a public page?

Ok -- I was just checking. I'll try to replicate your configuration on my side to see what I get for results.

Hi Nader, 

Alright I have reproduced your issue. I used the same setup that you specified above, however when I first did it, was working. But when I change the display type on teh asset publisher to "View in Context" it broke -- or rather it behaves the way you said, by challenging me to authenticate first. 

Looking at the URL though I can see that it uses 

http://localhost:8080/c/knowledge_base/find_kb_article?plid=20129&resourcePrimKey=105031&redirect=%2Fweb%2Fguest%2Fhome%3Fp_p_id%3Dcom_liferay_login_web_portlet_LoginPortlet%26p_p_lifecycle%3D0%26p_p_state%3Dnormal%26p_p_state_rcv%3D1

.. the leading /c indicates that it is a StrutsAction (service) that is being invoked. My guess is that it's challenging you for creds because that path is not listed as public. By default, struts actions services are private and if you want to make a path public, then you have to set the property auth.public.path to include the path you want to be unprotected. In Liferay with OSGI you can do this with a simple service. 

​​​​​​​@Component(
    immediate = true,
    property = {
        "auth.public.path=/knowledge_base/find_kb_article"
    },
    service = Object.class
)
public class KBPublicPath {
  // empty class -- used only to make teh knowledge base struts action path public
}

One thing to keep in mind though is that this will make this action public for all knowledge bases (on this site and others) because the struts action is a server level change. 

Let me know if that helps -- I didn't actuall try it on my side

Hi Nader,

That's good to hear. No, it's not wrong -- you can do it that way as well of course. The only downside to that approach is that you lose some of the awesome dynamism that Liferay gives you. By putting it in a module it allows you to turn the public path "on and off" at runtime without the need to restart the server. In your case though, it's probably not an issue because that KB is an out of the box feature -- but if you ever find yourself defining your own public paths, I would encourage you to use the module approach so that the paths come and go with the availability of your feature.

I thought about it a little more and there is one more thing to consider when using the portal-ext. With each release, more and more of the portal-ext properties are deprecated as they are moved into new models... Usually the control panel somewhere. So it might work now, but might stop working in an upgrade.

Hahaha .. well that's an argument for you to have with Liferay . If you really believe it to be an error, then I suggest you open a ticket at issues.liferay.com and state your case there