Hi All, +1 on storing XACML on file system. Yes, need to agree on deployment mechanism across the nodes.
We will not need a product UI for policy configuration. What we need is an offline tooling, preferably web based one; to make the life of the user easy; by hiding the perceived complexities of XML. We will be able to get all the IS configuration data (User Store, IdP, SP) to files in the same way. Cheers, Ruwan On Thu, Nov 10, 2016 at 7:58 AM, Harsha Thirimanna <[email protected]> wrote: > Hi All, > > In C4, we have stored the XACML policies in registry as resources and > maintained some meta data for each policy. > But in C5 , we were thinking to keep these files in file system as it is > as a deployment artifact for the user and load it in to the memory when the > server get start or on demand. But we have to maintain metadata for each > either in database or as a metafile in file system. > > What would be the best approach for this ? > > This may be again an common problem if we move registry resources to the > file system and may be solved in other product as well. > > If we move to file system, then we have think about the deployment model > for cluster. > Anyway we have to have some deployment model to share these kind of > artifact to each container like common mounting point to each container or > create new image for each policy changes since we take these container as > immutable. That is common problem for all the artifact deployment among the > cluster not only IS. > > Thanks > -- *Ruwan Abeykoon* *Associate Director/Architect**,* *WSO2, Inc. http://wso2.com <https://wso2.com/signature> * *lean.enterprise.middleware.*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
