I have been very slow in adopting Revo, but may have to do so soon as it seems to have better & more stable
features for my next project.
I really appreciate what the developers and all people involved have done to bring this very flexible system to the community. I truly enjoy using MODx and hope to give back to the community too!
I guess I have alot of reading and experimenting to do, but am sure there’s good advice lingering in some peoples’ heads
To quote the features that interested me most:
Enterprise-class Security, User Model & Authentication
Attribute Based Access Control lists (ABAC) gives site administrators granular control over every aspect of MODX Revolutions websites. Authentication can occur via the built in user system, Active Directory, LDAP, OpenID or virtually any other system that can use the MODX API.
Native JSON & Message Queue
MODX includes and leverages the native JSON processing to interact with other systems RESTfully. It’s simple, built-in Message Queue allows publishing messages and subscribing to a message bus for sophisticated interaction with external systems in Enterprise applications.
Could anyone share experiences or advice on integrating MODx Revo with internal systems?
What are your thoughts on sharing data between the website and systems? Particularly concerning security? I suppose there would be alot of heavy coding, hardening and enforcing policies to prevent any accidents or to stop any activities that are potentially malicious.
Any thoughts to share?
tino
