[
https://jira.jboss.org/jira/browse/TEIID-193?page=com.atlassian.jira.plug...
]
Steven Hawkins commented on TEIID-193:
--------------------------------------
That's close to what you would want (except you still need an aggregate
membershipservice concept to account for domain ordering). Representing something as a
service (either as individual MembershipServices or MembershipDomainServices) has
ramifications for it's configuration and creation that of course would require quite a
bit of work to do, that's why this keeps getting pushed.
MembershipService does not show failure in Console when unable to
connect to LDAP database
------------------------------------------------------------------------------------------
Key: TEIID-193
URL:
https://jira.jboss.org/jira/browse/TEIID-193
Project: Teiid
Issue Type: Feature Request
Components: Console
Affects Versions: 6.x
Reporter: Steven Hawkins
Priority: Minor
Fix For: 6.2.0
Defect Tracker #2865 : Set up MembershipService to have MetaMatrix and LDAP users.
Server PC was unable to communicate with Unix box hosting LDAP database. Server started
and MembershipService showed Running even though it had failed to read LDAP users. There
is an exception in MetaMatrixVM log but need a visual clue in Console.
--
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