[
https://issues.jboss.org/browse/JBIDE-25095?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-25095:
-------------------------------------
So I'm looking into this issue. The wf-common jars seem like a no-brainer to add.
However, the elytron private jars seem... controversial.
I've pinged [~ehugonnet] to see if this is reasonable. The obvious question is,
should it be private? If no, why is it? If yes, then why does your usecase require it?
Will wait to hear back from him.
WildFly 11 runtime should add
"wildfly-elytron-1.1.1.Final.jar" to build path
-----------------------------------------------------------------------------
Key: JBIDE-25095
URL:
https://issues.jboss.org/browse/JBIDE-25095
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: server
Affects Versions: 4.5.0.Final
Reporter: Wolfgang Knauf
Assignee: Rob Stryker
Priority: Minor
Fix For: 4.5.1.AM3
When a client app (e.g. a JavaEE application client) wants to perform a login to a
WildFly 11 server, it has to either use a "wildfly-config.xml" file or add some
code to setup security (see e.g. [Client authentication with Elytron
client|https://docs.jboss.org/author/display/WFLY/Client+Authentication+w...]
for a code snippet).
To make this code compile, two jar files are required:
%WILDFLY11_HOME%\modules\system\layers\base\org\wildfly\security\elytron-private\main\wildfly-elytron-1.1.1.Final.jar
%WILDFLY11_HOME%\modules\system\layers\base\org\wildfly\common\main\wildfly-common-1.2.0.Final.jar
I think the runtime should add them by default.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)