Hi Samual,
I'm really interested in alternatives. This is constantly evolving! How are
you going to define security without predefined roles?
Regards
Sander
--
You received this message because you are subscribed to the Google Groups
"Angular and AngularJS discussion" group.
To unsubscribe
So it seems you need to have roles beforehand, which means you need to make
api call to grape the roles. Is that best practice?
On Thursday, November 24, 2016 at 3:10:12 AM UTC-5, Felix Costa wrote:
>
> What is the best way to implement ACL / paper-based with angular 2?
>
>
> My scenario, in a
On Monday, November 28, 2016 at 4:51:35 AM UTC+1, Sander Elias wrote:
>
>
> I also add something like this to the css of the project, to prevent items
> from briefly flashing into view:
> [has-access] {
>display:none !importand
> }
>
>
>
Well this is a cool trick that I haven't thought of
Hi Leonardo,
It should work pretty seamless, I prefer bitmaps because they allow me to
very densely pack a load of boolean values. But an attribute approach is
using exactly the same semantics. You can draw a pattern for ACL pretty
easy, An actual implementation is tightly bound to your stack,
Hey, Sander:
I'm actually investigating about control-access patterns to apply a light
control-layer to my angular-app. As the Felix's needs, I want to know how
to manage component (enable/remove) based on the granted user permission. I
found that for an "elastic environment" there's is a
Hi Felix,
When it comes to ACL and auth, this is usually very tightly bound to the
project you need it in. I yet have to discover a generic solution for this.
(a workable one that is.)
I usually build a couple of services that use bitmasks to determine when a
user holds the right access
