[JBoss JIRA] (WFLY-4116) WAR deployment fails on missing security domain dependency
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-4116?page=com.atlassian.jira.plugin.... ]
jaikiran pai commented on WFLY-4116:
------------------------------------
The security-domain you have defined in your jboss-web.xml is incorrect. It should just be the name of the security domain. Change it to:
{code}
<jboss-web>
<security-domain>haa-portal</security-domain>
</jboss-web>
{code}
> WAR deployment fails on missing security domain dependency
> ----------------------------------------------------------
>
> Key: WFLY-4116
> URL: https://issues.jboss.org/browse/WFLY-4116
> Project: WildFly
> Issue Type: Feature Request
> Components: Security, Web (JBoss Web), Web (Undertow)
> Affects Versions: 8.2.0.Final
> Environment: Standalone form-based authentication WAR
> Reporter: Lars Hellgren
> Assignee: Darran Lofthouse
> Fix For: 8.2.0.Final
>
>
> Moving WARs using form based authentication from WildFly 8.1 Final to 8.2 Final fails due to a missing security domain dependency.
> *Log*
> {noformat}
> service jboss.security.security-domain.java:/jaas/haa-portal (missing) dependents:
> [service jboss.deployment.unit."haa-security-manager.war".component.SecurityManagerRepositorySessionBean.CREATE,
> service jboss.deployment.unit."haa-security-manager.war".component.UserPrefsRepository.CREATE]
> {noformat}
> *jboss-web.xml*
> {code:xml}
> <jboss-web>
> <security-domain>java:/jaas/haa-portal</security-domain>
> </jboss-web>
> {code}
> *standalone.xml*
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:security:1.2">
> <security-domains>
> ...
> <security-domain name="haa-portal">
> <authentication>
> <login-module code="Database" flag="required">
> ...
> </login-module>
> </authentication>
> </security-domain>
> </security-domains>
> </subsystem>
> {code}
> The datasource is deployed and connected.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 10 months
[JBoss JIRA] (WFLY-4116) WAR deployment fails on missing security domain dependency
by Lars Hellgren (JIRA)
Lars Hellgren created WFLY-4116:
-----------------------------------
Summary: WAR deployment fails on missing security domain dependency
Key: WFLY-4116
URL: https://issues.jboss.org/browse/WFLY-4116
Project: WildFly
Issue Type: Feature Request
Components: Security, Web (JBoss Web), Web (Undertow)
Affects Versions: 8.2.0.Final
Environment: Standalone form-based authentication WAR
Reporter: Lars Hellgren
Assignee: Darran Lofthouse
Fix For: 8.2.0.Final
Moving WARs using form based authentication from WildFly 8.1 Final to 8.2 Final fails due to a missing security domain dependency.
*Log*
{noformat}
service jboss.security.security-domain.java:/jaas/haa-portal (missing) dependents:
[service jboss.deployment.unit."haa-security-manager.war".component.SecurityManagerRepositorySessionBean.CREATE,
service jboss.deployment.unit."haa-security-manager.war".component.UserPrefsRepository.CREATE]
{noformat}
*jboss-web.xml*
{code:xml}
<jboss-web>
<security-domain>java:/jaas/haa-portal</security-domain>
</jboss-web>
{code}
*standalone.xml*
{code:xml}
<subsystem xmlns="urn:jboss:domain:security:1.2">
<security-domains>
...
<security-domain name="haa-portal">
<authentication>
<login-module code="Database" flag="required">
...
</login-module>
</authentication>
</security-domain>
</security-domains>
</subsystem>
{code}
The datasource is deployed and connected.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 10 months
[JBoss JIRA] (WFLY-1154) Allow the server to ignore files or groups of files at deployment time
by sathiya seelan (JIRA)
[ https://issues.jboss.org/browse/WFLY-1154?page=com.atlassian.jira.plugin.... ]
sathiya seelan commented on WFLY-1154:
--------------------------------------
Hi folks,
I want to start working on this issue.
What is the procedure or How to get start working?
Thanks
> Allow the server to ignore files or groups of files at deployment time
> ----------------------------------------------------------------------
>
> Key: WFLY-1154
> URL: https://issues.jboss.org/browse/WFLY-1154
> Project: WildFly
> Issue Type: Feature Request
> Components: Server
> Reporter: Marius Bogoevici
> Fix For: Awaiting Volunteers
>
>
> Legacy and migrated applications may occasionally contain files which are incompatible with the Java EE specification and can cause the application to fail the deployment. The difference between those cases and really faulty Java EE applications lies in the intent of the developer - whether they wish for those files to be picked up by the server and processed, or not.
> In such cases, it may be useful to expand the deployment specification and to be able to instruct the server to ignore particular files at deployment time.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 10 months
[JBoss JIRA] (WFLY-4115) WildFly 8.2.0.Final Maven artifacts are incomplete
by Harald Wellmann (JIRA)
Harald Wellmann created WFLY-4115:
-------------------------------------
Summary: WildFly 8.2.0.Final Maven artifacts are incomplete
Key: WFLY-4115
URL: https://issues.jboss.org/browse/WFLY-4115
Project: WildFly
Issue Type: Bug
Affects Versions: 8.2.0.Final
Reporter: Harald Wellmann
Assignee: Jason Greene
WildFly 8.2.0.Final artifacts in
{{https://repository.jboss.org/nexus/content/repositories/releases}}
are incomplete.
E.g. wildfly-embedded has a POM but no JARs.
wildfly-jaxrs has a JAR but no POM.
On Maven Central, there are neither JARs nor POMs for these two artifacts. wildfly-dist seems to be the only one that has made it to Central up to now.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 10 months
[JBoss JIRA] (WFCORE-276) whoami operation failed when rbac enabled but no roles assigned
by Darran Lofthouse (JIRA)
Darran Lofthouse created WFCORE-276:
---------------------------------------
Summary: whoami operation failed when rbac enabled but no roles assigned
Key: WFCORE-276
URL: https://issues.jboss.org/browse/WFCORE-276
Project: WildFly Core
Issue Type: Bug
Components: CLI, Domain Management
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 1.0.0.Alpha14
Need to double check this is either the CLI making a call in addition to the whoami op and that call is failing or something being accessed by whoami is causing the failure.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 10 months