logo
down
shadow

How to send sensitive data to a Liferay portlet from outside the Liferay portal


How to send sensitive data to a Liferay portlet from outside the Liferay portal

By : Beartok
Date : November 28 2020, 03:01 PM
To fix the issue you can do Secure IPC in Liferay
This is mostly a placeholder until you clarify your requirements and functional specifications. I am going to present some security essentials related to the Liferay platform and associated technologies. I will make the advice as general as possible however full disclosure the bulk of my experience is 6.2 EE.
code :
<entity name="Entity" remote-service="true" local-service="true">
auth.token.check.enabled=true
json.service.auth.token.enabled=true
auth.token.ignore.origins=.....
jsonws.web.service.strict.http.method=true
jsonws.web.service.invalid.http.methods=DELETE,POST,PUT
# Not necessarily filtering the above methods just an example
basic.auth.password.required=true
jsonws.web.service.public.methods=.....
son.servlet.hosts.allowed=....
json.servlet.https.required=true
jsonws.servlet.hosts.allowed=....
jsonws.servlet.https.required=true


Share : facebook icon twitter icon
Why am I getting a HotDeployException when I add a portlet.properties file to my portlet? (Liferay Portal Development)

Why am I getting a HotDeployException when I add a portlet.properties file to my portlet? (Liferay Portal Development)


By : Apps Quest Sdn Bhd
Date : March 29 2020, 07:55 AM
Any of those help Try removing the first slash: resource.actions.configs=resource-actions/default.xml double check that default.xml exists and that it is in a folder named resource-actions and that folder is under WEB-INF/src folder together with portlet.properties Open default.xml and make sure its internal structure is compliant with Liferay Resource Mapping DTD (prev. link is for Liferay 6.1)
Hide a portlet after logged into portal in liferay

Hide a portlet after logged into portal in liferay


By : Ercan
Date : March 29 2020, 07:55 AM
Hope this helps You can extend the portlet css only for this portlet, so that the portlet will be hidden when the user is sign-in.
Open portlet configuration (up-right) "Look-and-Feel" -> "Advenced Styling" and put under "Enter your custom CSS"
code :
.signed-in #portlet_INSTANCE_id {
    display: none;
}
Liferay portlet non-liferay JNDI data source null

Liferay portlet non-liferay JNDI data source null


By : user3756470
Date : March 29 2020, 07:55 AM
I wish this help you I just stumbled over this thread in the Liferay Forum which basically says. oput this in your tomcat/conf/server.xml
code :
<GlobalNamingResources>
<!-- Editable user database that can also be used by
     UserDatabaseRealm to authenticate users
-->
<Resource auth="Container" description="User database that can be updated and saved" factory="org.apache.catalina.users.MemoryUserDatabaseFactory" name="UserDatabase" pathname="conf/tomcat-users.xml" type="org.apache.catalina.UserDatabase"/>

<Resource name="jdbc/XXX" auth="Container" type="javax.sql.DataSource"
          maxActive="20" maxIdle="10" maxWait="5000"
          removeAbandoned="true" removeAbandonedTimeout="250" validationQuery="SELECT 1"
          username="user2" password="pwd2"
          driverClassName="com.mysql.jdbc.Driver"
          url="jdbc:mysql://localhost/myOtherDb"/>    
<ResourceLink name="jdbc/XXX" global="jdbc/XXX" type="javax.sql.DataSource">
how to redirect from jsp of one portlet to jsp of another portlet inside liferay module project in liferay 7

how to redirect from jsp of one portlet to jsp of another portlet inside liferay module project in liferay 7


By : user1758304
Date : March 29 2020, 07:55 AM
Hope that helps If you separate the two portlets into two different modules, you should treat the JSPs of the other module as an implementation detail, e.g. you can't reach it (even if there'd be a way to reach them).
If the two portlets are tightly coupled and should share their implementation details, you can easily deploy them as a single module. This signals to anybody maintaining them, that they're required to be deployed together. Otherwise you might end up with one portlet being incomplete because the other portlet updated and nobody was aware that a JSP was used by some external component.
How to backport a 6.1.1 jsf portlet to get it running on a 6.1.0 liferay portal?

How to backport a 6.1.1 jsf portlet to get it running on a 6.1.0 liferay portal?


By : Safiullah Warraich
Date : March 29 2020, 07:55 AM
I wish this helpful for you It's probably easier to recompile the portlet in the 6.1.0 sdk. Especially when you use ServiceBuilder: you're running with a code generator that is probably relying on the runtime files that come matching runtime to generated code.
For pure JSR-286 portlets, they are easily compatible even across major versions. If you use more sophisticated code, e.g. ServiceBuilder or the API, lots of effort is taken to keep it compatible, but no guarantee can be given that it actually is binary compatible - sorry, that's life.
shadow
Privacy Policy - Terms - Contact Us © voile276.org