Projects tagged ‘jndi’

Project Open Provisioning ToolKit (OpenPTK) is an open source User Provisioning Toolkit exposing API's, Web Services, HTML Taglibs, JSR-168 Portlets with user self-service and administration examples. ... [More] The architecture supports several pluggable back-end services including Sun's Identity Manager, Sun's Access Manager and LDAPv3. [Less]

Ldap Synchronization Connector (LSC) reads from any data source including databases, LDAP directories or files and transforms and compares this data to an LDAP directory. These connectors can then be ... [More] used to continuously synchronize a data source to a directory, for a one shot import or just to compare differences by outputting CSV or LDIF format reports. LSC offers a powerful transformation engine, based on a scripting language, to easily manipulate data on the fly. Various identity management functions are included for directory-specific compatibility — most notably Active Directory (changing passwords, account status, last logon, etc …). LSC is an open source project written in Java, available under the BSD license. [Less]

Scriptella is an ETL (Extract-Transform-Load) and script execution tool. Its primary focus is simplicity. It doesn't require the user to learn another complex XML-based language to use it, but allows ... [More] the use of SQL or another scripting language suitable for the data source to perform required transformations. Main features: * Simple and minimalistic XML syntax for ETL scripts. * Built-in providers for JDBC, CSV, Text, XML, LDAP, Lucene and Velocity. * Support for many useful JDBC features, e.g. parameters in SQL including file blobs and JDBC escaping. * Easy-to-Use as a standalone tool or Ant task. No deployment/installation required. Easy-To-Run ETL files directly from Java code. * Seamless integration with Java/Java EE and Spring [Less]

Inspired by the JavaSpaces API, this project aims to provide a tiny library enabling developers to read, write and take objects from a remote store. Not based on Jini, it is less featured but should ... [More] be easier to get started with. Example usage: // The Space TinySpace ts = TinySpaceFinder.find(); // Store an object that implements Entry Message m = new Message(); m.message = "test"; ts.write(m); // Retrieve that object by specifying an object with some matching properties. Message s = new Message(); s.message = "test"; Message x = (Message) ts.read(s);User_Manual [Less]

A simple JSP that allows to browse the JNDI namespace and do lookups.

OverviewThis simple webapp is intended to be used in a J2EE/Java EE container, in order to test DataSource objects available in a JNDI context. It allows one to type a JNDI name and a SQL SELECT ... [More] query and outputs the result in a tabular form. InstallationSimply deploy the WAR archive (available in the downloads section) to your J2EE container / application server. It should work out of the box. For example, on JBoss, you just need to copy the DataSourceTester-0.0.1-SNAPSHOT.war file to $JBOSS_HOME/server/default/deploy/ and the application will become available on http://yourserveraddress.example.com/DataSourceTester-0.0.1-SNAPSHOT/ UsageAfter opening the main web page, you'll see a web form with two text fields labeled DataSource JNDI name and Test query text. After you fill them in, press the Test DataSource button. If the query succeeds, its results will be shown below in tabular form. Deinstallation / undeploymentDepends on the kind of application server. On JBoss, you just have to delete the DataSourceTester-0.0.1-SNAPSHOT.war file from the $JBOSS_HOME/server/default/deploy/ directory. DisclaimerWARNING: Deploy this application on your server only after you have understood all its security implications! This application does not authenticate the user in any way and allows to send arbitraty queries to any DataSource available through public JNDI contexts. Don't deploy it on a publically available server, and undeploy it immediately after use. Alternatively, you can employ container provided authentication and authorization mechanisms (e.g. JAAS and J2EE role based security) but you have to do this on your own and the authors of DataSourceTester provide no support for this since most of this is container specific (e.g. for JBoss you can use similar approach as for securing the JMX and Web console). The author gives no guarantees for the proper functioning nor take any responsibility for damages resulting from the use of this application. For details, see the LICENSE file. You have been warned. [Less]

The default JNDI Authenticator is not sufficient for more advanced operations required for a secure webapp, including the obtaining of web-app roles.

Simply JNDI based Object/Hierarchy Mapping Framework

This is a Java library that aims to provide a minimal wrapper around JNDI for accessing LDAP. This project aims to have no other dependencies other than the standard Java library.

This is a module for OpenCms that contains a flexible data source widgetThe module contains a user interface widget that allows select list pull-down data to be obtained from dynamic data sources. The ... [More] module contains a single widget which is configurable and extensible by adding data sources. Three data sources are included in the module: A data source that obtains data from a repeated field within a structured content item A data source that returns a list of structured content types A data soruce that returns selection data using a database query The widget also contains a framework for adding additional data sources. Installing the moduleDownload the binary module. Import the module into OpenCms using Administrator/Module management tools Register the widget with OpenCms: * Edit the file: \WEB-INF\config\opencms-vfs.xml * Locate the section * Add the widget registration: * Restart OpenCmsThe /Widgets folder contains samples showing various ways to use the widgets. ==Using the widget To use the widget, the layout section of the schema file must contain a reference to the widget. The configuration will look like this: DATA_SOURCE must be the name of a Java class that implements the I_WidgetSelectSource interface. The module includes the following three data sources: com.efoundry.widgets.sources.ContentFieldListDS This data source retrieves select option values obtained from a repeating field in a structured content instance. The configuration string specifies where the data comes from. The syntax of the configuration string is: contenttype - this must specify the structured content type that contains the list of values to be returned location - this specifies the location of the resource instance. The resource instance must be of the specified contenttype fieldname - this specifies the name of the field within the contenttype containing the values. The field must be a simple type containing a string value A 'ChoiceList' content type is included in the module which may be used to contain select list values. Configuration Example: configuration="source='com.efoundry.widgets.sources.ContentFieldListDS'|contenttype='ChoiceList'|location='/Widgets/Seminars'|fieldname='Value'" the contenttype is set to 'ChoiceList' the instance containing the data is located at '/Widgets/Seminars' the field within the content type is named 'Value' com.efoundry.widgets.sources.ContentTypesDS Configuration Example: configuration="source='com.efoundry.widgets.sources.ContentTypesDS|exclude='xmlpage'" This data source returns a selection list that contains a list of content types. The 'source' and 'exclude' parameters are delimited with a | character. The 'exclude' parameter contains a comma separated list of content types that are to be excluded from the list. the exclude option is used to filter out the xmlpage content type com.efoundry.widgets.sources.DatabaseTableDS This data source obtains select list values using a database query. The 'source', 'jndiname', and 'qry' parameters are delimited with a | character. The 'jndiname' parametercontains a name of the JNDI resource that is used for the data connection, and the qry contains the query to be used. The data source obtains the name of the option value from the first returned column, and the value from the second one. Any other columns used in the query are ignored. Configuration Example: configuration="source='com.efoundry.widgets.sources.DatabaseTableDS'|jndiname='jdbc/states'|qry='select state,name from states'" the JNDI resource name is 'jdbc/states' the query is 'select state,name from states' Adding new data sourcesAdding a new data source is simply a matter of creating a java class that implements the I_WidgetSelectSource interface. public interface I_WidgetSelectSource { /** * This method is called after the data source is constructed and before the option values are * retrieved. It passes along the configuration string to the widget. * * @param config String value of the configuration string */ public void setConfiguration(CustomSourceConfiguration config); /** * Returns a List of {@link SelectOptionValue} objects to be displayed in the * selection list. */ public List getValues(CmsObject cms); } [Less]