Ramsey,
I've just finished watching you WOWODC ’13 presentation on Ponder. That’s exactly what I need. Congratulations for the framework and presentation. I’ll just use a R2D2W app for user management, as I don’t need a fancy layout. And I’ll get password reset and other fancy features for free! :-) Now I just have to figure out how to use ERUsers and ERAuth with an ERRest app. Once I get that sorted out, I’ll be ready to go. Cheers, Flavio > On 05/10/2015, at 18:32, Ramsey Gurley <[email protected]> wrote: > > ERUsers can probably do what you want. You would create a role named Admin > and then override the > > 10 : (entity.model.name = 'ERUsers' or pageConfiguration = 'CreateERUser') => > crudAuthorization = "er.users.delegates.AuthorizationDelegate.INSTANCE" > [ERDEnumAssignment] > > rule with something like > > 100: (entity.model.name = ‘ERUsers’ and > session.objectStore.user.roles.roleName contains ‘Admin’) => > crudAuthorization = “er.auth.SimpleCRUDAuthorization.ALLOW_ALL” > [ERDEnumAssignment] > > or some other CRUDAuthorization instance that allows you to do what you want. > > On Oct 5, 2015, at 1:18 PM, Flavio Donadio <[email protected]> wrote: > >> I must be insane! I didn’t mean ERGroupware, but Ponder! >> >> Please, replace any occurrence of “ERGroupware” with “Ponder” in my original >> text. >> >> Sorry for the noise. >> >> Flavio >> >> >>> On 05/10/2015, at 17:08, Flavio Donadio <[email protected]> wrote: >>> >>> Hello, >>> >>> >>> I am on the planning stage of a new REST-web-service-based app with a Cocoa >>> client. >>> >>> In my head, it makes sense to have a web interface (a Direct Action or D2W >>> app) just for user management, where the administrative users would be able >>> to create/edit/delete users and specify their abilities (which entities a >>> user can fetch/create/edit/delete, maybe with roles support). From what >>> I’ve seen, ERGroupware is able to do just that. Am I correct? >>> >>> In my ERRest routes [in the ERRest (main) app], I would check if the user >>> has the necessary ability and act accordingly. I could also have some >>> properties on the client-side app (Cocoa-based) that would drive the UI >>> (enable or disable UI elements) based on user’s abilities/role. >>> >>> Is my logic good so far? Is this feasible? >>> >>> >>> Regards, >>> Flavio >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Webobjects-dev mailing list ([email protected]) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/webobjects-dev/flavio%40donadio.com.br >>> >>> This email sent to [email protected] >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list ([email protected]) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/rgurley%40smarthealth.com >> >> This email sent to [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
