[JBoss JIRA] (ELY-1523) Update the JAPICMP settings so that we only detect changes that break API compatibility
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-1523?page=com.atlassian.jira.plugin.s... ]
Jan Kalina commented on ELY-1523:
---------------------------------
Problem is {{breakBuildBasedOnSemanticVersioning}} parameter, which sets allowed changes by version numbers:
Because newVersion is 1.2.1.Final and oldVersion is 1.2.1.SP1 (all three parts of the version are same), japicmp requires level UNCHANGED, which mean any change in classes breaks build.
This also mean, that if newVersion and oldVersion would have different major version, it would allow API breaking changes!
Going to set checked level manually, independent on version names.
> Update the JAPICMP settings so that we only detect changes that break API compatibility
> ---------------------------------------------------------------------------------------
>
> Key: ELY-1523
> URL: https://issues.jboss.org/browse/ELY-1523
> Project: WildFly Elytron
> Issue Type: Task
> Components: Build
> Reporter: Farah Juma
> Assignee: Jan Kalina
>
> Currently, the JAPICMP settings will result in a build failure if new public API has been added. As we will be tagging .Final releases more regularly, we need to be able to allow new public API into a patch release so we should only be detecting changes that break API compatibility not changes that add new public API.
> As an example, try building the 1.2.1.Final tag (https://github.com/wildfly-security/wildfly-elytron/tree/1.2.1.Final). The build will fail due to new public API unless the -DskipCompatibility flag is passed in.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3667) Wildfly 12 : jboss-cli.sh in infinite loop
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3667?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise updated WFCORE-3667:
-----------------------------------------
Priority: Critical (was: Major)
> Wildfly 12 : jboss-cli.sh in infinite loop
> -------------------------------------------
>
> Key: WFCORE-3667
> URL: https://issues.jboss.org/browse/WFCORE-3667
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Environment: ubuntu 16.06 lxd container
> java version "1.8.0_161" oracle
> v12 migrated from v11
> Reporter: Gaétan QUENTIN
> Assignee: Jean-Francois Denise
> Priority: Critical
> Labels: regression
> Attachments: aesh-readline-1.5.jar, jboss-cli-logging.properties, jboss-cli.25300, term.txt
>
>
> i cannot use anymore the jboss-cli.sh to connect to the contoller since i migrated from v11 to with wildfly 12:
>
> wildfly@java2:/opt/Wildfly$ ls -la
> drwxr-xr-x 1 root root 156 Mar 3 20:36 jboss-server-migration
> drwxr-xr-x 1 root root 454 Mar 4 00:09 overlays
> drwxr-xr-x 1 root root 166 Mar 4 11:43 scripts
> drwxr-xr-x 1 root root 236 Oct 24 05:30 wildfly-11.0.0.Final
> drwxr-xr-x 1 root root 236 Mar 1 07:29 wildfly-12.0.0.Final
> lrwxrwxrwx 1 root root 20 Mar 4 12:49 wildfly-current -> wildfly-12.0.0.Final
>
>
> my wildfly management console is on 172.20.12.192.
> v12 has been migrated from v11 with the jboss-server-migration tool. Applications and app manager works fine and the wildfly instance controller is well binded on the requested ip.
>
>
> with wildfly-current link on -> wildfly-11.0.0.Final:
>
> this works perfectly:
> (cd /opt/Wildfly/wildfly-current/bin && ./jboss-cli.sh -c -u=xx -p=xx --controller=http-remoting://172.20.12.192:9990)
>
>
> with wildfly-current -> wildfly-12.0.0.Final:
> this go in infinite loop until crash :
> (cd /opt/Wildfly/wildfly-current/bin && ./jboss-cli.sh -c -u=xx -p=xx --controller=http-remoting://172.20.12.192:9990)
>
> output:
>
> '[standalone@172.20.12.192:9990' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] '[standalone@172.20.12.192:9990' is not a valid operation name.
> ''[standalone@172.20.12.192:9990'' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] ''[standalone@172.20.12.192:9990'' is not a valid operation name.
> '[standalone@172.20.12.192:9990' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] '''[standalone@172.20.12.192:9990''' is not a valid operation name.
> ''''[standalone@172.20.12.192:9990'''' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] ''[standalone@172.20.12.192:9990'' is not a valid oper is not a valid operation name.
> '[standalone@172.20.12.192:9990' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] '''''[standalone@172.20.12.192:9990''''' is not a valid operation name.
> ''''''[standalone@172.20.12.192:9990'''''' is not a valid operation name.
> attached is a strace capture file (one of thousands) of jboss-cli .
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3667) Wildfly 12 : jboss-cli.sh in infinite loop
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3667?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise moved WFLY-9949 to WFCORE-3667:
----------------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-3667 (was: WFLY-9949)
Component/s: CLI
(was: CLI)
Affects Version/s: (was: 12.0.0.Final)
> Wildfly 12 : jboss-cli.sh in infinite loop
> -------------------------------------------
>
> Key: WFCORE-3667
> URL: https://issues.jboss.org/browse/WFCORE-3667
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Environment: ubuntu 16.06 lxd container
> java version "1.8.0_161" oracle
> v12 migrated from v11
> Reporter: Gaétan QUENTIN
> Assignee: Jean-Francois Denise
> Labels: regression
> Attachments: aesh-readline-1.5.jar, jboss-cli-logging.properties, jboss-cli.25300, term.txt
>
>
> i cannot use anymore the jboss-cli.sh to connect to the contoller since i migrated from v11 to with wildfly 12:
>
> wildfly@java2:/opt/Wildfly$ ls -la
> drwxr-xr-x 1 root root 156 Mar 3 20:36 jboss-server-migration
> drwxr-xr-x 1 root root 454 Mar 4 00:09 overlays
> drwxr-xr-x 1 root root 166 Mar 4 11:43 scripts
> drwxr-xr-x 1 root root 236 Oct 24 05:30 wildfly-11.0.0.Final
> drwxr-xr-x 1 root root 236 Mar 1 07:29 wildfly-12.0.0.Final
> lrwxrwxrwx 1 root root 20 Mar 4 12:49 wildfly-current -> wildfly-12.0.0.Final
>
>
> my wildfly management console is on 172.20.12.192.
> v12 has been migrated from v11 with the jboss-server-migration tool. Applications and app manager works fine and the wildfly instance controller is well binded on the requested ip.
>
>
> with wildfly-current link on -> wildfly-11.0.0.Final:
>
> this works perfectly:
> (cd /opt/Wildfly/wildfly-current/bin && ./jboss-cli.sh -c -u=xx -p=xx --controller=http-remoting://172.20.12.192:9990)
>
>
> with wildfly-current -> wildfly-12.0.0.Final:
> this go in infinite loop until crash :
> (cd /opt/Wildfly/wildfly-current/bin && ./jboss-cli.sh -c -u=xx -p=xx --controller=http-remoting://172.20.12.192:9990)
>
> output:
>
> '[standalone@172.20.12.192:9990' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] '[standalone@172.20.12.192:9990' is not a valid operation name.
> ''[standalone@172.20.12.192:9990'' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] ''[standalone@172.20.12.192:9990'' is not a valid operation name.
> '[standalone@172.20.12.192:9990' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] '''[standalone@172.20.12.192:9990''' is not a valid operation name.
> ''''[standalone@172.20.12.192:9990'''' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] ''[standalone@172.20.12.192:9990'' is not a valid oper is not a valid operation name.
> '[standalone@172.20.12.192:9990' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] '''''[standalone@172.20.12.192:9990''''' is not a valid operation name.
> ''''''[standalone@172.20.12.192:9990'''''' is not a valid operation name.
> attached is a strace capture file (one of thousands) of jboss-cli .
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9949) Wildfly 12 : jboss-cli.sh in infinite loop
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFLY-9949?page=com.atlassian.jira.plugin.... ]
Jean-Francois Denise commented on WFLY-9949:
--------------------------------------------
[~gquentin], I think I reproduced your issue and attempted a fix. Would you be kind enough to try it?
2 steps:
- Copy a safe original jar: cp wildfly-current/modules/system/layers/base/org/aesh/main/aesh-readline-1.5.jar ./orig-aesh-readline-1.5.jar
- Then replace it with the attached one: cp aesh-readline-1.5.jar wildfly-current/modules/system/layers/base/org/aesh/main/aesh-readline-1.5.jar
Thank-you to let me know how it went in order to integrate the fix properly.
JF
> Wildfly 12 : jboss-cli.sh in infinite loop
> -------------------------------------------
>
> Key: WFLY-9949
> URL: https://issues.jboss.org/browse/WFLY-9949
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 12.0.0.Final
> Environment: ubuntu 16.06 lxd container
> java version "1.8.0_161" oracle
> v12 migrated from v11
> Reporter: Gaétan QUENTIN
> Assignee: Jean-Francois Denise
> Labels: regression
> Attachments: aesh-readline-1.5.jar, jboss-cli-logging.properties, jboss-cli.25300, term.txt
>
>
> i cannot use anymore the jboss-cli.sh to connect to the contoller since i migrated from v11 to with wildfly 12:
>
> wildfly@java2:/opt/Wildfly$ ls -la
> drwxr-xr-x 1 root root 156 Mar 3 20:36 jboss-server-migration
> drwxr-xr-x 1 root root 454 Mar 4 00:09 overlays
> drwxr-xr-x 1 root root 166 Mar 4 11:43 scripts
> drwxr-xr-x 1 root root 236 Oct 24 05:30 wildfly-11.0.0.Final
> drwxr-xr-x 1 root root 236 Mar 1 07:29 wildfly-12.0.0.Final
> lrwxrwxrwx 1 root root 20 Mar 4 12:49 wildfly-current -> wildfly-12.0.0.Final
>
>
> my wildfly management console is on 172.20.12.192.
> v12 has been migrated from v11 with the jboss-server-migration tool. Applications and app manager works fine and the wildfly instance controller is well binded on the requested ip.
>
>
> with wildfly-current link on -> wildfly-11.0.0.Final:
>
> this works perfectly:
> (cd /opt/Wildfly/wildfly-current/bin && ./jboss-cli.sh -c -u=xx -p=xx --controller=http-remoting://172.20.12.192:9990)
>
>
> with wildfly-current -> wildfly-12.0.0.Final:
> this go in infinite loop until crash :
> (cd /opt/Wildfly/wildfly-current/bin && ./jboss-cli.sh -c -u=xx -p=xx --controller=http-remoting://172.20.12.192:9990)
>
> output:
>
> '[standalone@172.20.12.192:9990' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] '[standalone@172.20.12.192:9990' is not a valid operation name.
> ''[standalone@172.20.12.192:9990'' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] ''[standalone@172.20.12.192:9990'' is not a valid operation name.
> '[standalone@172.20.12.192:9990' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] '''[standalone@172.20.12.192:9990''' is not a valid operation name.
> ''''[standalone@172.20.12.192:9990'''' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] ''[standalone@172.20.12.192:9990'' is not a valid oper is not a valid operation name.
> '[standalone@172.20.12.192:9990' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] '''''[standalone@172.20.12.192:9990''''' is not a valid operation name.
> ''''''[standalone@172.20.12.192:9990'''''' is not a valid operation name.
> attached is a strace capture file (one of thousands) of jboss-cli .
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9949) Wildfly 12 : jboss-cli.sh in infinite loop
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFLY-9949?page=com.atlassian.jira.plugin.... ]
Jean-Francois Denise updated WFLY-9949:
---------------------------------------
Attachment: aesh-readline-1.5.jar
> Wildfly 12 : jboss-cli.sh in infinite loop
> -------------------------------------------
>
> Key: WFLY-9949
> URL: https://issues.jboss.org/browse/WFLY-9949
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 12.0.0.Final
> Environment: ubuntu 16.06 lxd container
> java version "1.8.0_161" oracle
> v12 migrated from v11
> Reporter: Gaétan QUENTIN
> Assignee: Jean-Francois Denise
> Labels: regression
> Attachments: aesh-readline-1.5.jar, jboss-cli-logging.properties, jboss-cli.25300, term.txt
>
>
> i cannot use anymore the jboss-cli.sh to connect to the contoller since i migrated from v11 to with wildfly 12:
>
> wildfly@java2:/opt/Wildfly$ ls -la
> drwxr-xr-x 1 root root 156 Mar 3 20:36 jboss-server-migration
> drwxr-xr-x 1 root root 454 Mar 4 00:09 overlays
> drwxr-xr-x 1 root root 166 Mar 4 11:43 scripts
> drwxr-xr-x 1 root root 236 Oct 24 05:30 wildfly-11.0.0.Final
> drwxr-xr-x 1 root root 236 Mar 1 07:29 wildfly-12.0.0.Final
> lrwxrwxrwx 1 root root 20 Mar 4 12:49 wildfly-current -> wildfly-12.0.0.Final
>
>
> my wildfly management console is on 172.20.12.192.
> v12 has been migrated from v11 with the jboss-server-migration tool. Applications and app manager works fine and the wildfly instance controller is well binded on the requested ip.
>
>
> with wildfly-current link on -> wildfly-11.0.0.Final:
>
> this works perfectly:
> (cd /opt/Wildfly/wildfly-current/bin && ./jboss-cli.sh -c -u=xx -p=xx --controller=http-remoting://172.20.12.192:9990)
>
>
> with wildfly-current -> wildfly-12.0.0.Final:
> this go in infinite loop until crash :
> (cd /opt/Wildfly/wildfly-current/bin && ./jboss-cli.sh -c -u=xx -p=xx --controller=http-remoting://172.20.12.192:9990)
>
> output:
>
> '[standalone@172.20.12.192:9990' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] '[standalone@172.20.12.192:9990' is not a valid operation name.
> ''[standalone@172.20.12.192:9990'' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] ''[standalone@172.20.12.192:9990'' is not a valid operation name.
> '[standalone@172.20.12.192:9990' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] '''[standalone@172.20.12.192:9990''' is not a valid operation name.
> ''''[standalone@172.20.12.192:9990'''' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] [standalone@172.20.12.192:9990 /] ''[standalone@172.20.12.192:9990'' is not a valid oper is not a valid operation name.
> '[standalone@172.20.12.192:9990' is not a valid operation name.
> [standalone@172.20.12.192:9990 /] '''''[standalone@172.20.12.192:9990''''' is not a valid operation name.
> ''''''[standalone@172.20.12.192:9990'''''' is not a valid operation name.
> attached is a strace capture file (one of thousands) of jboss-cli .
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (ELY-1537) PolicyContext.getContext("javax.security.auth.Subject.container")
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/ELY-1537?page=com.atlassian.jira.plugin.s... ]
Martin Choma commented on ELY-1537:
-----------------------------------
org.wildfly.security.auth.server.SecurityDomain seems to be public API to me. At least package is guarded against changes by japicmp tool during build [1].
{code:module.xml}
<module xmlns="urn:jboss:module:1.5" name="org.wildfly.security.elytron">
<dependencies>
<module name="org.wildfly.security.elytron-private" services="export" export="true">
<exports>
<include-set>
<path name="org/wildfly/security"/>
<path name="org/wildfly/security/auth"/>
<path name="org/wildfly/security/auth/callback"/>
<path name="org/wildfly/security/auth/client"/>
<path name="org/wildfly/security/auth/permission"/>
<path name="org/wildfly/security/auth/principal"/>
<path name="org/wildfly/security/auth/server"/>
<path name="org/wildfly/security/auth/server/event"/>
<path name="org/wildfly/security/auth/util"/>
<path name="org/wildfly/security/authz"/>
<path name="org/wildfly/security/credential"/>
<path name="org/wildfly/security/credential/source"/>
<path name="org/wildfly/security/credential/store"/>
<path name="org/wildfly/security/evidence"/>
<path name="org/wildfly/security/http"/>
<path name="org/wildfly/security/key"/>
<path name="org/wildfly/security/manager"/>
<path name="org/wildfly/security/manager/action"/>
<path name="org/wildfly/security/mechanism"/>
<path name="org/wildfly/security/password"/>
<path name="org/wildfly/security/password/interfaces"/>
<path name="org/wildfly/security/password/spec"/>
<path name="org/wildfly/security/permission"/>
<path name="org/wildfly/security/sasl/util"/>
<path name="org/wildfly/security/ssl"/>
</include-set>
</exports>
</module>
<module name="org.wildfly.common" export="true" />
<module name="org.wildfly.client.config" export="true"/>
</dependencies>
</module>
{code}
[1] https://github.com/wildfly-security/wildfly-elytron/blob/master/pom.xml#L579
> PolicyContext.getContext("javax.security.auth.Subject.container")
> -----------------------------------------------------------------
>
> Key: ELY-1537
> URL: https://issues.jboss.org/browse/ELY-1537
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.2.3.Final
> Reporter: Ilia Vassilev
> Assignee: Darran Lofthouse
>
> PolicyContext.getContext("javax.security.auth.Subject.container") returns null when using elytron to protect a web application.
> This should return the authenticated subject.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (ELY-1537) PolicyContext.getContext("javax.security.auth.Subject.container")
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/ELY-1537?page=com.atlassian.jira.plugin.s... ]
Martin Choma edited comment on ELY-1537 at 3/5/18 11:31 AM:
------------------------------------------------------------
org.wildfly.security.auth.server.SecurityDomain seems to be public API to me. At least package is guarded against changes by japicmp tool during build [1].
{code:title=module.xml}
<module xmlns="urn:jboss:module:1.5" name="org.wildfly.security.elytron">
<dependencies>
<module name="org.wildfly.security.elytron-private" services="export" export="true">
<exports>
<include-set>
<path name="org/wildfly/security"/>
<path name="org/wildfly/security/auth"/>
<path name="org/wildfly/security/auth/callback"/>
<path name="org/wildfly/security/auth/client"/>
<path name="org/wildfly/security/auth/permission"/>
<path name="org/wildfly/security/auth/principal"/>
<path name="org/wildfly/security/auth/server"/>
<path name="org/wildfly/security/auth/server/event"/>
<path name="org/wildfly/security/auth/util"/>
<path name="org/wildfly/security/authz"/>
<path name="org/wildfly/security/credential"/>
<path name="org/wildfly/security/credential/source"/>
<path name="org/wildfly/security/credential/store"/>
<path name="org/wildfly/security/evidence"/>
<path name="org/wildfly/security/http"/>
<path name="org/wildfly/security/key"/>
<path name="org/wildfly/security/manager"/>
<path name="org/wildfly/security/manager/action"/>
<path name="org/wildfly/security/mechanism"/>
<path name="org/wildfly/security/password"/>
<path name="org/wildfly/security/password/interfaces"/>
<path name="org/wildfly/security/password/spec"/>
<path name="org/wildfly/security/permission"/>
<path name="org/wildfly/security/sasl/util"/>
<path name="org/wildfly/security/ssl"/>
</include-set>
</exports>
</module>
<module name="org.wildfly.common" export="true" />
<module name="org.wildfly.client.config" export="true"/>
</dependencies>
</module>
{code}
[1] https://github.com/wildfly-security/wildfly-elytron/blob/master/pom.xml#L579
was (Author: mchoma):
org.wildfly.security.auth.server.SecurityDomain seems to be public API to me. At least package is guarded against changes by japicmp tool during build [1].
{code:module.xml}
<module xmlns="urn:jboss:module:1.5" name="org.wildfly.security.elytron">
<dependencies>
<module name="org.wildfly.security.elytron-private" services="export" export="true">
<exports>
<include-set>
<path name="org/wildfly/security"/>
<path name="org/wildfly/security/auth"/>
<path name="org/wildfly/security/auth/callback"/>
<path name="org/wildfly/security/auth/client"/>
<path name="org/wildfly/security/auth/permission"/>
<path name="org/wildfly/security/auth/principal"/>
<path name="org/wildfly/security/auth/server"/>
<path name="org/wildfly/security/auth/server/event"/>
<path name="org/wildfly/security/auth/util"/>
<path name="org/wildfly/security/authz"/>
<path name="org/wildfly/security/credential"/>
<path name="org/wildfly/security/credential/source"/>
<path name="org/wildfly/security/credential/store"/>
<path name="org/wildfly/security/evidence"/>
<path name="org/wildfly/security/http"/>
<path name="org/wildfly/security/key"/>
<path name="org/wildfly/security/manager"/>
<path name="org/wildfly/security/manager/action"/>
<path name="org/wildfly/security/mechanism"/>
<path name="org/wildfly/security/password"/>
<path name="org/wildfly/security/password/interfaces"/>
<path name="org/wildfly/security/password/spec"/>
<path name="org/wildfly/security/permission"/>
<path name="org/wildfly/security/sasl/util"/>
<path name="org/wildfly/security/ssl"/>
</include-set>
</exports>
</module>
<module name="org.wildfly.common" export="true" />
<module name="org.wildfly.client.config" export="true"/>
</dependencies>
</module>
{code}
[1] https://github.com/wildfly-security/wildfly-elytron/blob/master/pom.xml#L579
> PolicyContext.getContext("javax.security.auth.Subject.container")
> -----------------------------------------------------------------
>
> Key: ELY-1537
> URL: https://issues.jboss.org/browse/ELY-1537
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.2.3.Final
> Reporter: Ilia Vassilev
> Assignee: Darran Lofthouse
>
> PolicyContext.getContext("javax.security.auth.Subject.container") returns null when using elytron to protect a web application.
> This should return the authenticated subject.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months