[
https://jira.jboss.org/browse/TEIID-1245?page=com.atlassian.jira.plugin.s...
]
Ramesh Reddy resolved TEIID-1245.
---------------------------------
Resolution: Rejected
The problem exists with the AS code, when it does the "testConnection" call on
its managed pool. Even when a "security-domain" is not defined for a connection
factory like the "text-file" connection, AS tries to create a assume a dummy
security domain called "other" and tries to validate a "null" user
thus gets into this exception. AS should only make use of the "security-domain"
and validate against it, when it is defined in the connection factory's
configuration.
This same behaviour can be observed on any connection factory with out a security-domain.
However, if one defines a security domain then they must configure a
"org.jboss.resource.security.ConfiguredIdentityLoginModule" or
"CallerIdentityLoginModule", so that they can supply the credentials to login
into the connection factory.
Text connection factory defined here does not require secure access. If it needs to be
secure, it is user's responsibility to add the additional security by defining the
"security-domain".
exception trying to get a test connection through admin console to a
text file based connection factory
-------------------------------------------------------------------------------------------------------
Key: TEIID-1245
URL:
https://jira.jboss.org/browse/TEIID-1245
Project: Teiid
Issue Type: Bug
Components: Connector API
Affects Versions: 7.1
Environment: RHEL5, openjdk, SOA-P 5.1dev3
Reporter: Aleksandar Kostadinov
Assignee: Ramesh Reddy
Fix For: 7.1.1
Attachments: exception.txt
I'm not completely sure there is a bug and if it is in teiid or admin console but it
looks like a confusing behavior. When someone deploys a text file based connection factory
like this attached to TEIID-1242 and without modifying login-config.xml, then trying to
get a test connection results in an exception in the server log (see attached
exception.txt).
If login-config.xml is modified to have the "other" application policy be the
same as the "soa" policy, then this error does not appear in the server log.
I'm not sure where should policy name be configured but IMHO user should be able to
perform admin console actions by default given she/he is logged in as admin to the
console.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira