This content has been marked as final.
Show 2 replies
-
1. Re: Seam 2.3.1.Final <restrict> with 3rd party authentication
vata2999 Feb 20, 2016 12:59 AM (in response to johncarl81)By setting security-enabled to false Identity component is almost useless.
Seam doesn't do any magic for restrictions it only checks a simple boolean which you can get from
Expressions.instance().createValueExpression(expr, Boolean.class).getValue();
unless you are using permissions which in this case, I think you can create a custom component with permission store to get what you need, then use Seam permissionMapper.
components.xml
<component name="org.jboss.seam.security.persistentPermissionResolver" class="org.jboss.seam.security.permission.PersistentPermissionResolver"> <property name="permissionStore">#{customPermissionStore}</property> </component>
@Name("customPermissionStore") @Install(value = true) @Scope(APPLICATION) @BypassInterceptors public class CustomPermissionStore extends JpaPermissionStore { .... }
that's all I know.
-
2. Re: Seam 2.3.1.Final <restrict> with 3rd party authentication
johncarl81 Apr 26, 2016 6:37 PM (in response to vata2999)After trying the approach Omid suggested and another technqiue using Prettyfaces to restrict page access, we ended up using Prettyfaces:
Pretty URLs for JavaServer Faces and Java Application Servers | OCPsoft