[JBoss JIRA] Created: (GTNPORTAL-332) Generate one ear per distribution kind : single-node, clustering
by Dimitri BAELI (JIRA)
Generate one ear per distribution kind : single-node, clustering
----------------------------------------------------------------
Key: GTNPORTAL-332
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-332
Project: GateIn Portal
Issue Type: Task
Components: Packaging
Affects Versions: 3.0.0-Beta03
Reporter: Dimitri BAELI
Assignee: Dimitri BAELI
Fix For: 3.0.0-Beta04
DESCRIPTION:
* Current GateIn packaging contains only the single-node configuration
* The configuration of clustering is not available (in comments or ready to use) in the packaging
EXPECTED:
* Ready to use configuration to switch GateIn in a cluster mode (changes in the configuration prepared in comments)
* Ready to use configured ear packaged during the gatein build (a gatein-<version>-ha.ear)
INFORMATIONS:
Some configurations are distincts between usages and should be easy to change or prepared for most of the users:
* Clustering configuration
* Database configuration
* WSRP configuration (tomcat/jboss)
* date/temp directories (tomcat/jboss)
NOTES:
* This work should be linked to the packager rework and a clean-up of gatein maven build
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (GTNPORTAL-256) Replace the exopackage structure with maven tooling
by Dimitri BAELI (JIRA)
Replace the exopackage structure with maven tooling
---------------------------------------------------
Key: GTNPORTAL-256
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-256
Project: GateIn Portal
Issue Type: Task
Components: Packaging
Reporter: Dimitri BAELI
Assignee: Dimitri BAELI
Fix For: 3.0.0-CR01
Current GateIn packaging is done using an exopackage tooling (scripting written in javascript).
This tooling is hard to maintain and should be replaced by a more maintainable tooling (maven / java).
EXPECTED:
* Include the tooling in gate to ease its replacement by a more convenient tooling and avoid the need to update an external tool in GateIn dependencies
* Then review the used functionalities and replace them by common maven features or a dedicated maven plugin
TARGET:
* All this code should be gone for Gate 3.0 GA
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (GTNPORTAL-854) Login Exception when input invalid password in Sign In form
by Hang Nguyen (JIRA)
Login Exception when input invalid password in Sign In form
-----------------------------------------------------------
Key: GTNPORTAL-854
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-854
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Security
Reporter: Hang Nguyen
Assignee: Julien Viet
Fix For: 3.0.0-GA
- Go to http://localhost:8080/portal/public/classic/
- Click Sign In form
- Input user name: root
- Input password: abc
- Click Sign In
- Return to form of private mode --> OK
- Input valid pass: gtn
- Click Sign In button
=> Can't login to portal and return to http://localhost:8080/portal/private/j_security_check.
Show exception in cygwin:
WARNING: Login exception authenticating username "null"
javax.security.auth.login.LoginException
at org.exoplatform.services.security.jaas.DefaultLoginModule.commit(DefaultLoginModule.java:
155)
at org.exoplatform.services.security.j2ee.TomcatLoginModule.commit(TomcatLoginModule.java:47
)
at sun.reflect.GeneratedMethodAccessor343.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
at javax.security.auth.login.LoginContext.login(LoginContext.java:580)
at org.apache.catalina.realm.JAASRealm.authenticate(JAASRealm.java:363)
at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:2
58)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:417)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.ja
va:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months