[jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-799) security documentation issues

Shane Bryzak (JIRA) jira-events at lists.jboss.org
Fri Feb 9 09:38:30 EST 2007


     [ http://jira.jboss.com/jira/browse/JBSEAM-799?page=all ]

Shane Bryzak reassigned JBSEAM-799:
-----------------------------------

    Assignee: Shane Bryzak

> security documentation issues
> -----------------------------
>
>                 Key: JBSEAM-799
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-799
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Documentation, Security
>    Affects Versions: 1.1.6.GA
>            Reporter: Stephan Bublava
>         Assigned To: Shane Bryzak
>            Priority: Minor
>
> Some minor issues I stumbled upon while reading the documentation, which is quite excellent, btw.
> 1) Using your container's JAAS configuration (12.2.5.1)
> I believe the configuration example is wrong: "jaasConfigName" should be "jaas-config-name". In this case "authenticate-method" should not be present at all.
> 2) The @Restrict annotation (12.3.2.1.)
> The documentation does not mention which permission check will be invoked if @Restrict is placed on the class. (Is this equivalent to  adding @Restrict to each method?)
> 3) Creating a security rules file (12.4.3)
> The security rule in this section differs from those in seamspace (no-loop, activation-group, modify(c)). I assume the last one is essential.
> 4) Since Seam 1.1.6 it's possible to redirect to the original page after login (JBSEAM-773). It would be great to have an example in the documentation.

-- 
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

        



More information about the seam-issues mailing list