Hi markfoertein,
Thanks for your response.
Yes, I´m from Brasil too (Curitiba). It would be very interesting share my
experience using seam with you. Please send a mail to [EMAIL PROTECTED] so we
can start a talk.
tks
emerson fabiano
View the original post :
http://www.jboss.com/index.htm
Well, not quite, but what was really happening isn't far from weird.
I managed to solve the problem by changing from this:
GrantedPermission(n : name -> (n == check.getName()), a : action -> (a ==
check.getAction()))
To this:
GrantedPermission(n : name -> (n.equals(check.getName())), a : action
Hi,
I had the same issue and I found the problem.
When security system is checking this
GrantedPermission(n : name -> (n == check.getName()), a : action -> (a
| == check.getAction()))
only the first argument (n == check.getName()) is verified.
best regards
emerson fabiano
View the origi
>From what I can see everything looks ok. If you could post your code (even
>better if it will build) to JIRA I'd be happy to look at it for you. I've got
>Michael Neale (from the Drools team) probably coming over next Monday so if I
>can't work out what's wrong I'm sure he'd be happy to take
Hi Shane / guys,
I really would appreciate any help with this.
I have everything set. The role's permissions are on the database, I defined
actions to manipulate this permissions through the UI, etc...
The "authenticate" method is doing his job, putting all permissions into the
working memory.
That did the trick, but now Im facing another problem.
When the user authenticates, his roles and its permissions are loaded, and a
new GrantedPermission object is asserted for each permission into the working
memory:
| public boolean authenticate() {
| ...
|
| for (SphGru
Try check.getName() and check.getAction(). We're waiting for the next Drools
milestone to be released which should include some enhancements to the rule
language that will allow more EL-like expressions.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043399#
Hi Shane,
Today I finally got my hands on this. My database structure and entities are
all set.
Step 2) tricked me, since the getSecurityContext() method is not available
inside RuleBasedIdentity.instance(). So Im using the following to get the
working memory:
| WorkingMemory wm = ((RuleBas
It makes sense and looks like a good solution. I was thinking that the
permissions, coming from the database, would be stored in memory somehow,
somewhere... but I couldn't realize how to accomplish that so I could make the
checks later ;-)
I will try to implement it and see what happens, then
There's an outstanding JIRA issue to add this kind of functionality to Seam
security, however you can easily implement it in your own application.
Roughly, the steps are:
1) Create a Permission class with a name and action property. For this example
let's call it GrantedPermission.
2) In your
Hi Shane,
I don't know what stsheak wants exactly, but I was about to ask a similar
question, so I will use this topic instead of opening a new one.
I've successfully implemented authentication and authorization using Seam
security. It works great.
I defined my roles on the database and bound
What exactly do you want to achieve? The fact that authorization is rule-based
means that it should provide a great deal of flexibility. Can you describe
what your requirements are?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025776#4025776
Reply to the
12 matches
Mail list logo
