[teiid-issues] [JBoss JIRA] Resolved: (TEIID-664) Add "membership" service

[ https://jira.jboss.org/jira/browse/TEIID-664?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIID-664. -------------------------------- Resolution: Done Membership service added to the "embedded" profile. It adds following properties to deploy.properties. This service is enabled by default. # Enables the membership, where the logins must be authenticated membership.enabled=true # admin/super user creadentails membership.superUser=admin membership.superUserPassword=teiid # Various domain providers can be specified with comma separated list (ex: file, ldap) membership.DomainOrder=file # you can restrict access only to certain hosts #membership.allowedHosts= Every domain provider can define three properties to define their membership implementation. File, LDAP are provided by Teiid and example properties below. The domain class is initialized and contents of the property file are passed for its configuration. You can define any number of membership domains in single Teiid instance. During the authentication time, they will be invoked in the order they are defined to authenticate the user. # File Membership Provider file.activate=false file.AuthDomainClass=com.metamatrix.platform.security.membership.spi.file.FileMembershipDomain file.propertiesFile=./deploy/membership-file.properties # LDAP Membership provider ldap.activate=false ldap.AuthDomainClass=com.metamatrix.platform.security.membership.spi.ldap.LDAPMembershipDomain ldap.propertiesFile=./deploy/membership-ldap.properties -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira