I'm currently building a website for a company, that will for the moment contain 3-5 static pages (i.e, just content). User registration may be added in time to come.
Now, I've been reading through the Liferay docs, forums and wiki, and I'm still pretty unclear on the approach to take in designing this website:
If I were to model my company Website as an organization in Liferay where I would have the public pages of the Website, what would be the purpose of the default guest page? (/web/gues/home)? Do I remove this and redirect the guest to my organization? If so, how do I do this?
Who is the creator of an organization in the real world? Is this site administrator? or the person responsible for adding content?
Who is the creator of an organization in Liferay? Is this the administrator to Liferay (i.e the default Test user)?
The best way to do is is to put your pages in the Public Pages of your organization and setup a virtual host (see Manage Pages -> Virtual Hosts in the Control Panel) for those pages. This way, www.my-homepage.com will redirect to the public pages of your organization. You should of course be owner of the domain and link the domain to the IP address of the server the website runs on.
In Liferay, by default only users with the role of Administrator can add organizations. For managing content you should setup other roles. Create f.e. a Content Editor role and add permissions for the Web Content portlet (Create Content, Approve, Edit, Delete, View in Control Panel). This also answered your third question.
Add this lines of code in your portal-ext.properties
mail.session.mail.pop3.host=pop.gmail.com
mail.session.mail.pop3.password=PASSWORD
mail.session.mail.pop3.port=110
mail.session.mail.pop3.user=USER
mail.session.mail.imap.host=imap.gmail.com
mail.session.mail.imap.port=993
mail.session.mail.store.protocol=imap
mail.session.mail.transport.protocol=smtp
mail.session.mail.smtp.host=smtp.gmail.com
mail.session.mail.smtp.password=PASSWD
mail.session.mail.smtp.user=USERID#gmail.com
mail.session.mail.smtp.port=465
mail.session.mail.smtp.auth=true
mail.session.mail.smtp.starttls.enable=true
mail.session.mail.smtp.socketFactory.class=javax.net.ssl.SSLSocketFactory
Please user your password in place of PASSWD and your gmail user id in place of USERID.
By three different ways we can configure mail server in Liferay. I am using Liferay 6.2 and initially I got an error that could not connect to smtp host localhost port 25 in liferay by using different code. So I used above code and my mail server is configured properly and my application is able to send mail to the user in forgot password case.
And please see this link. This link help me to solve the issue.
https://www.permeance.com.au/web/tim.telcik/home/-/blogs/how-do-i-configure-liferay-portal-to-use-google-mail
Thanks
asif aftab
Related
i have developed a portal using Liferay.I have two kind of users, guest user and Admin user. The login should be possible by the Admin only. The guest user should not be able to login , or even see the sign in button. How do i achieve this? through different url's?
You might consider the following approach:
Remove the login portlet from the theme template. (portal-normal.vm)
Create a hidden page on your Guest group. On this page you place only the login portlet. So only the people who know the direct URL are able to login. AFAIK there is no other way to achieve this, as you don't know if someone is an Admin before he entered his credentials ;)
[EDIT]
To remove the login portlet from the template you have to do the following steps:
A) If you don't have a custom theme
- Create a new Theme
- Parent of your new theme is classic
- Place portal_normal.vm in /docroot/_diffs/templates
- Remove these lines:
#if (!$is_signed_in)
<a data-redirect="$is_login_redirect_required" href="$sign_in_url" id="sign-in" rel="nofollow">$sign_in_text</a>
#end
That should remove the login link.
- Compile and deploy your theme
- Assign the theme to the portal as default theme. Assign the theme to your guest group Site.
Now you only have to create your hidden page and place the login portlet on it.
[/EDIT]
You can also consider an alternative approach if you know sth more about the admin users - e.g. their IP address / addresses, then you could modify the contents of a page in a similar manner as stated by Gevatterjan, but then you check not for the signed-in users, but the ones with specfic IPs.
What is the code to configure these configurations from the coding site in liferay java? Without going through the settings in admin's panel?
To configure restrictions using code. At MAIN MENU- CONFIGURATION from the admin site. But how to configure each permission for owner, portal content reviewer, portal user and others for add to page, configuration, view and permissions using code either in controller or xml?
For example to restrict view, certain page, or others.
Thanks.
Two components
Liferay site
Another web-site on which we do not have any control
What we have
We would be using apache-httpcomponents to login to the website programmatically through Liferay and get the html page after login. Do some HTML parsing and display the page in liferay.
What we need to do (and this is were i need help or pointers)
So what we need to do is this :
User logs in to Liferay giving credentials
He will only be logged-in when the login is successful in the other website programatically.
Once login successful in that application, a session would be created in liferay.
Once the user is idle for a certain period and is logged-out of website it should log the user out from Liferay as well.
User base is the same in both the website and liferay but password in liferay are different and not same as those in the website.
Also is my approach correct when I am using Apache HttpComponents or is there any other way to do this?
Any help in this direction would help.
Thanks
Note: Cross-posted on Liferay Forums - Maintain Liferay session depending upon session in another website
I'm not sure which is your problem. Liferay log out users automatically when they stop interacting for a time.
When I place a test AD account in the Visitors group they are unable to view any pages on my new intranet site. The users receives the "Error access denied" sharepoint screen and indicates that the account was able to authenticate, but that some authorisation rule is permitting it from viewing the page.
When i remove then and place them in the Members or Owners groups they are able to view the pages as well as perform the expected functions like editing content and creating subsites.
Interesting, while in only the Visitors group, users can view the "All Site Content" page that is located here: /_layouts/viewlsts.aspx but not /pages/default.aspx.
Has anyone experienced this before?
Environment info:
1 Web application, 1 Site collection using the Publishing Portal template. A few custom master pages, lots of custom page layouts and user controls. All deployed via features.
Sharepoint 2010 Standard edition, 64bit running on Windows Server 2008 against SqlServer 2008 Enterprise Edition. Authentication is against AD, not any other forms auth providers etc.
One likely reason for such behavior is that it tries to access a resource on a page which might not have been published to a major version. For example, if versioning was turned on on images library and an image's version is 0.1, if that image was used on version 1.0 (published) of the page, the server would deny access to the visitor and ask for credentials.
Make sure following:
At least one major version of the page exists (page was published at least once)
All resources (images, movie files etc) used on the page are published (to major version)
You can use "Draft Check" button on Page Tab of the Page's ribbon to check the unpublished resources that are used by the page.
I had the same issue and I've finaly found out how to do this:
If you check OOB group access, you can find that Visitors group has limited number of pages where it has granted access.
Navigate to /yourweb/_catalogs/masterpage. Here you'll find many
.aspx files (including default.master).
Open this default.master`s permissions and you see it inherits from
Master Page Gallery.
Click this permissions inheritance and you can see that Master Page
Gallery permissions are not inherited from site collection
permissions.
Give here the Contribute permissions to Style Resource Readers (or
modify it as you'd like) and all users will have access to this web
with no permissions to edit etc..
I had a similar issue and the thing I noted in your Environmental comments was the custom master pages. Go to your Site Settings and ensure that your custom master pages have been published. If you need to publish them also check the corresponding html pages after they have been published as they may need to be republished also.
This worked for me.
I have enabled anonymous users on the farm and on the entire site.
I also have Windows Authentication turned on.
Whenever an anonymous user attempts to view the site, they are prompted to log in.
And they get prompted to login on every single page they view.
I would like to allow users to log in via Windows Authentication, (perhaps through a special page), but anonymous users should not get prompted to put in their password ever.
Does that mean I need to switch to forms based authentication for the entire site, or is there an option in 2010 to somehow get Windows Authentication and allowing anonymous users to live harmoniously.
It could be because some of the file is not published. For ex, if master page, CSS stylesheet or any image is unpublished, it will prompt the user for login.
Make sure everything is published and it will work.
You need to see if it is anything on this path http://server/_catalogs/masterpage/Forms/AllItems.aspx
that it is not published.
You must publish everything
May be you missed some of the configuration steps .So i wish if you take a look to the following article
SP2010 Branding Tip #9 – Turn on Anonymous Access
Regards
I assume that you are using the Publishing Site Template for the public site and hence the default.aspx (the welcome page of all the subsites) is not published so you would need to start the approval workflow publish the pages and any other assets (master page, css, images etc)
You need to do some prepwork to set the site up using two web applications, both with different authentication methods. You can't run SharePoint effectively for Windows users and anonymous (or Forms based authentication) at the same time.
Essentialy:
Create your SharePoint site for internal users using Windows Authentication
Extend the site to a new site (using the same content database) but using anonymous or forms based authentication (whichever makes sense for you)
A MSDN article can be found here on this:
http://msdn.microsoft.com/en-us/library/ff648385.aspx
You can also read Andrew Connell's blog about this (he talks about Forms based authentication but you can do the same with anonymous access)
http://www.andrewconnell.com/blog/articles/HowToConfigPublishingSiteWithDualAuthProvidersAndAnonAccess.aspx
Basically you want dual authentication, Windows for one set of users and anonymous or FBA for another (and each access the site using a different URL)
Hope that helps.