[JBoss JIRA] (SRAMP-450) S-ramp installer && S-ramp-distro add fabric as a new target
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/SRAMP-450?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on SRAMP-450:
----------------------------------
We need to make sure any common tasks for fabric are placed in the overlord-commons installer.
Currently RTGov doesn't require the keystore, so possibly it doesn't need to go in commons. If DTGov leverages the configuration done by SRAMP, then maybe it only needs to be in SRAMP for now?
Otherwise the keystore should be created in commons, and the sramp installer just setup the property file.
The other thing to note is that the overlord-commons installer may be called multiple times, if different overlord sub-projects are being installed. So we need to ensure it only runs once.
> S-ramp installer && S-ramp-distro add fabric as a new target
> ------------------------------------------------------------
>
> Key: SRAMP-450
> URL: https://issues.jboss.org/browse/SRAMP-450
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: David virgil naranjo
> Assignee: David virgil naranjo
>
> Create a new target deployment in both the s-ramp-installer and s-ramp-distro-assembly.
> The Fabric deployment needs to unzip the overlord-commons.profile zip and the s-ramp-profile.zip inside the fabric installation.
> The question is, what to do with the keystore and the references to the keystore from the sramp-ui.properties?
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (SRAMP-450) S-ramp installer && S-ramp-distro add fabric as a new target
by David virgil naranjo (JIRA)
David virgil naranjo created SRAMP-450:
------------------------------------------
Summary: S-ramp installer && S-ramp-distro add fabric as a new target
Key: SRAMP-450
URL: https://issues.jboss.org/browse/SRAMP-450
Project: S-RAMP
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: David virgil naranjo
Assignee: David virgil naranjo
Create a new target deployment in both the s-ramp-installer and s-ramp-distro-assembly.
The Fabric deployment needs to unzip the overlord-commons.profile zip and the s-ramp-profile.zip inside the fabric installation.
The question is, what to do with the keystore and the references to the keystore from the sramp-ui.properties?
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (RTGOV-476) java.lang.IllegalStateException: No LoginService for org.eclipse.jetty.security.authentication.FormAuthenticator@
by David virgil naranjo (JIRA)
[ https://issues.jboss.org/browse/RTGOV-476?page=com.atlassian.jira.plugin.... ]
David virgil naranjo commented on RTGOV-476:
--------------------------------------------
This error appears in the normal flow of fuse fabric deploying. But it dissapears when the deployment is debugged and there are breakpoints in to the jetty-all jar.
Steps to follow to deploy without error and check that the application is deployed correctly:
Steps
- The s-ramp commit has not been merged yet. You can download my development from:
https://github.com/dvirgiln/s-ramp/tree/SRAMP-423
Or we can wait Brett will merge on monday.
Compile s-ramp and overlord-commons (the head is ok).
-Extract the zip in the fuse profiles folder
- Execute karaf console. Inside karaf execute these commands:
fabric:create --zookeeper-password admin
fabric:container-create-child --jvm-opts '-Xms1000m -Xmx1000m -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n' root dd
-Debug the s-ramp code in eclipse as remote application port 8787.
-Download the jetty-all jar attach as source in the eclipse debug.
-Import the breakpoints from the file attached. In case there is an error in the importing, the important ones are:
- AggregateLifeCycle 184
- LoginAuthenticator 59 and 61 --> The one that throws the Login Service Not found
- SegurityHandler 121 259 287 --> The one that calls the findLoginService
- org.eclipse.jetty.server.Server 513 --> Reads the data from the overlord-jetty.xml.
Then in the karaf console:
fabric:container-add-profile dd overlord-sramp
If you debug the code, in the logs:
fuse_install/instances/dd/data/log/karaf.log you ll not see any exception.
If you add the profile in the child container without debugging, then the exception appears.
If the application is deployed without any error and you want to test s-ramp in the browser you have to add to the user that you created the fabric the overlorduser role:
jaas:manage --index 3
jaas:roleadd user_name overlorduser
jaas:update
Then normally in the http://localhost:8182/s-ramp-ui/ should be deployed the application.
> java.lang.IllegalStateException: No LoginService for org.eclipse.jetty.security.authentication.FormAuthenticator@
> -----------------------------------------------------------------------------------------------------------------
>
> Key: RTGOV-476
> URL: https://issues.jboss.org/browse/RTGOV-476
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Reporter: Gary Brown
> Assignee: David virgil naranjo
> Fix For: 2.0.0.Final
>
>
> When RTGov all configuration is deployed in a fabric child container we get the following exception:
> java.lang.IllegalStateException: No LoginService for org.eclipse.jetty.security.authentication.FormAuthenticator@3afffabb in org.eclipse.jetty.security.ConstraintSecurityHandler@7ba6293f
> at org.eclipse.jetty.security.authentication.LoginAuthenticator.setConfiguration(LoginAuthenticator.java:61)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years