[JBoss JIRA] (WFCORE-2582) jboss-cli.bat script is unable to start on Windows, if JBOSS_HOME folder contains '!' character
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2582?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on WFCORE-2582:
-------------------------------------------------
Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1440757|https://bugzilla.redhat.com/show_bug.cgi?id=1440757] from VERIFIED to CLOSED
> jboss-cli.bat script is unable to start on Windows, if JBOSS_HOME folder contains '!' character
> -----------------------------------------------------------------------------------------------
>
> Key: WFCORE-2582
> URL: https://issues.jboss.org/browse/WFCORE-2582
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Jean-Francois Denise
> Assignee: Jean-Francois Denise
> Fix For: 3.0.0.Beta12
>
>
> jboss-cli.bat script is unable to start on Windows, if JBOSS_HOME folder contains '!' character, if '!' character is not at the end of the name of JBOSS_HOME folder.
> jboss-cli.bat script is unable to start on Windows if JBOSS_HOME ends with exclamation mark, but it is covered by JBEAP-249
> {noformat}
> C:\Users\Administrator\playground\7.1.0.DR15\jboss!eap\bin>jboss-cli.bat
> The system cannot find the path specified.
> The system cannot find the path specified.
> Could not locate "C:\Users\Administrator\playground\7.1.0.DR15\jbosseap\bin\jboss-modules.jar".
> Please check that you are in the bin directory when running this script.
> Press any key to continue . . .
> C:\Users\Administrator\playground\7.1.0.DR15\jboss!eap\bin>jboss-cli.bat
> {noformat}
> * This issue is caused by JBEAP-9699
> *Workaround:*
> Rename JBOSS_HOME folder
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-1173) InvalidNameState not used for non-existing identities in ServerAuthenticationContext
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-1173?page=com.atlassian.jira.plugin.s... ]
Jan Kalina updated ELY-1173:
----------------------------
Summary: InvalidNameState not used for non-existing identities in ServerAuthenticationContext (was: InvalidNameState not used for non-existing identities)
> InvalidNameState not used for non-existing identities in ServerAuthenticationContext
> ------------------------------------------------------------------------------------
>
> Key: ELY-1173
> URL: https://issues.jboss.org/browse/ELY-1173
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Critical
>
> There was added new state *InvalidNameState* into *ServerAuthenticationContext* as part of ELY-1115, but it is currently used only when principal is rewritten to null - not when identity is not found in security realm.
> After adding this will be probably necessary to implement more State methods in *InvalidNameState* to have wildfly tests green.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-1173) InvalidNameState not used for non-existing identities
by Jan Kalina (JIRA)
Jan Kalina created ELY-1173:
-------------------------------
Summary: InvalidNameState not used for non-existing identities
Key: ELY-1173
URL: https://issues.jboss.org/browse/ELY-1173
Project: WildFly Elytron
Issue Type: Bug
Reporter: Jan Kalina
Assignee: Jan Kalina
Priority: Critical
There was added new state *InvalidNameState* into *ServerAuthenticationContext* as part of ELY-1115, but it is currently used only when principal is rewritten to null - not when identity is not found in security realm.
After adding this will be probably necessary to implement more State methods in *InvalidNameState* to have wildfly tests green.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month