[ http://jira.jboss.com/jira/browse/RHDS-337?page=comments#action_12390437 ] Anatoly Fedosik commented on RHDS-337: -------------------------------------- "Further Reading" chapter was adding. It has the links to other guides. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/RHDS-337?page=comments#action_12390461 ] Anatoly Fedosik commented on RHDS-337: -------------------------------------- I'm confused with section 3.6. in Getting Started Guide. Michael Yuan wrote: "Section 3.6 uses the LoggedInInterceptor to manage authorization. This is not the way to do it. You should use declarative security in pages.xml. (read the "simplified mode" part in http://docs.jboss.com/seam/1.2.1.GA/reference/en/html/security.html)" As I understand from Seam Guide: We need to add in component.xml <security:identity authenticate-method="#{authenticator.authenticate}"/> and then to wtrite an authentication method. pages.xml is configured only to redirect security errors. Simplified Configuration - Summary So to sum up, there are the three easy steps to configure authentication: * Configure an authentication method in components.xml. * Write an authentication method. * Write a login form so that the user can authenticate. Is it enough for 3.6 section in GSG? What part of code should I show? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/RHDS-337?page=comments#action_12390809 ] Michael Yuan commented on RHDS-337: ----------------------------------- Anatoly, The pages.xml file can be used to configure which web pages require login. Like this: <pages xmlns="http://jboss.com/products/seam/pages" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.com/products/seam/pages http://jboss.com/products/seam/pages-2.0.xsd" login-view-id="/login.xhtml"> ... ... <page view-id="/protected.xhtml" login-required="true"/> </pages> That is the simplest use case for Seam security. cheers Michael -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/RHDS-337?page=comments#action_12390895 ] Anatoly Fedosik commented on RHDS-337: -------------------------------------- Recommendation for using Seam in 4 and 5 chapters added as <note> in the beginning of text. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira