[ https://issues.jboss.org/browse/TEIID-1749?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1749: --------------------------------------- After porting this for a while it seems like it mostly does not belong in the Teiid docs. We could expand on our admin security doc section to clarify a few points, but the attached: 1. assumes eds 2. assumes the use of the file LoginModule for both Teiid and as a fallback for SOA/AS. This is against our docs which explicitly say that file should not be used for production. Do we have a SOA guideline on this? 3. the ldap parts could be more easily folded into the existing community/project docs, such as http://community.jboss.org/docs/DOC-11253 and http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5..., or be treated as a quick-start specific to EDS. In short, I'm inclined to make minor changes to our doc rather than incorporating this in whole. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1749?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1749. ----------------------------------- Resolution: Done Expanded the admin guide section on built-in login modules. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira