Based on Wicket and JCR, it is the ONLY Wicket-based CMS framework available today. BRIX was built on the idea of "Power versus Complexity", providing for ease of use while at the same time allowing designers the highest degree of freedom in developing a rich user experience.
Current StatusThe first drop (0.0.14) has been delivered, it is a public beta version. Please go to Downloads pages to get it and have a try! Next step, I will write a pluggable XACML policy editor. If you have any ideas about it, please send an email to me, thanks.
... [More] Java XACML is intent to fully implement OASIS XACML 2.0 (I will support XACML 3.0 in the future), and provide a high performance and good usability that can be used in enterprise environment. Note, this is a totally independent implementation. It does NOT rely on Sun's XACML implementation or any other implementations.
FeaturesFully implemented XACML 2.0 core standard, passed all conformance tests. Provided PDP that can accept XACML requests and return XACML responses. Highly effective target in [Less]
Strategic and secure information sources are naturally becoming key repositories that customers want to make searchable. Since search is a platform and not just an application commodity, it is a pre-requisite to cope with heterogeneous security systems in order to seamlessly roll-out an
... [More] Enterprise-wide secure search capability.
The search appliance can nicely integrate with popular single sign-on (SSO) systems, forms-based authentication systems and negotiate HTTP Basic and NTLM authentications/authorizations. However, it can’t substitute the need for a unified authentication process across all secure sources. Heterogeneous sources may require different sets of credentials which make the search experience painful for the end-user, having to authenticate multiple times when querying.
Additionally, the appliance may not be able in certain cases to cope with complex and non-standard authentication and/or authorization processes which may put at risk the deployment of search technology.
The GSA (Google Search Appliance) Valve Security Framework was designed to answer both of these issues. It exposes a global authentication capability to the search user and then loads transparently the sets of credentials that are relevant to each indexed sources. It is a framework that can easily be extended to support the specifics of new repositories in terms of authentication and authorization processes.
This authentication and authorization framework acts as a content proxy and can be considered as a quick, simple and low-cost alternative to a single sign-on (SSO) system. It can be integrated as well with third-party SSO solutions in those situations where the corporate SSO doesn’t secure all the searchable applications.
It offers two different interfaces to be integrated with the appliance: Forms Based and SAML. You can use any of them using the GSA integration features.
You can use Authentication/Authorization modules created by third party contributors. There is a file in the download area that includes the current ones, like the Oracle Portal module. These modules don't have anything to do with the connectors provided with the GSA Connector Manager < http://code.google.com/p/google-enterprise-connector-manager/ > as they have different purposes.
Last Version: 2.0 (June 20 2008) [Less]
This open source project provides an extensible mechanism to crawl content located in multiple secure sources with the same server instance. This tool acts as a proxy server that is in between the crawler (i.e. the Google Search Appliance) and the content sources, letting you fully customize the way
... [More] the access to these sources is done at crawling time. This proxy is completely independent of the way the content is served.
It extends the crawling options natively implemented in the crawler, taking the advantage of the connectivity provided by the Authentication/Authorization modules for the GSA Valve Security Framework < http://code.google.com/p/gsa-valve-security-framework/ >. These modules implement the integration complexity to securely access to the content sources where documents are. The GSA Crawl Proxy is able to authenticate the crawler user coming from the search appliance using HTTP Basic, and send those credentials to any of these modules that can convert them to any security mechanism the content servers would understand.
Latest version: 1.0 (June 2008) [Less]