[
https://issues.apache.org/jira/browse/GERONIMO-5256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Godik updated GERONIMO-5256:
--
Attachment: geronimo-wadi-cl-bug.logs.tar.gz
geronimo-wadi-cl-bug-war.tar.gz
Issue Type: Bug
Security Level: public (Regular issues)
Affects Versions: 2.1.4
Environment: redhat 5.4, suse 11.2
Reporter: Simon Godik
If object placed in a http session implements java.io.Externalizable and is
loading web-app specific classes from the
I'm having difficulty building 1.0.0 tag. Dependencies are missing: commons-fileupload-1.1-dev.jar, dwr-1.0.jar, org.apache.geronimo.specs/geronimo-corba_2.3_spec/1.0/jarI did not get past corba dependency. Any special instructions for
1.0 tag?Simon
Hi Hernan,
Whatever user id you are using to log into the Geronimo is not defined in
your database; (line 199 SQLLoginModule throwing an exception). Make sure
that something is selected with the user-select query that is an option for
the sql-login-module.
Simon
>
Joe Bohn wrote:
>I'm
not sure if these charts are helpful for anybody else or not. It's
>a
point in time snapshot that I created of parent (import) dependencies
>between
configurations at the moment (which some of the changes that I
>have
pending to clean up some dependencies).
>
Trust rules for csi-v2:
We derive B from Kb by authentication (Kb => B); B controls A means that B
is trusted on A;
B|A means B is quoting A; (or) B says A says s; B|A is a quoting principal;
(Abadi etal)
B is auth token identity;
A is identity token identity;
Backward trust:
Kb => B;
Local Trust
Hi David,
>Can you elaborate
>how we will support both forward and backward styles using the login
>service for both?
With the csi-v2 we can have transport principal, auth-principal, and
identity token principal; Transport principal is authenticated by the
transport protocol, auth principal w
My impression is that CORBA security implementation (csi-v2) is not
integrated well with the Geronimo login service (please correct me if I'm
wrong). I plan to integrate csi-v2 security with the Geronimo login service
by having csi-v2 interceptor authenticate with the login service and thus
have co
Here is an outline of the login-service and authentication by assertion;
There are at least 2 use cases for authentication by assertion: SAML and
CSI-V2;
SAML defines browser profile for inter-domain transfer: user agent is
transferred from the source site in one domain to the destination site in
Not sure what you mean by the 'interceptor would be creating one of these
(subjects?)'
I want to emphasize that interceptors (or any code for that matter) should
be passed authenticated subject(s) and hopefully we can avoid a call to
ContextManager.registerSubject() altogether;
The only calls an
When default and run-as principals are in-effect they should be treated the
same way as any other principal; (eg granting of privilege to perform
certain tasks); That means we should track these objects in the
login-service and believe that these objects are authentic; We rely on the
login-service
externalize sensitive data out of the deployment plans
--
Key: GERONIMO-1488
URL: http://issues.apache.org/jira/browse/GERONIMO-1488
Project: Geronimo
Type: New Feature
Versions: 1.1
Reporter: simon
create gbean-permission
---
Key: GERONIMO-1487
URL: http://issues.apache.org/jira/browse/GERONIMO-1487
Project: Geronimo
Type: New Feature
Versions: 1.1
Reporter: simon godik
create gbean-permission.
--
This message is
create secure vault gbean
-
Key: GERONIMO-1486
URL: http://issues.apache.org/jira/browse/GERONIMO-1486
Project: Geronimo
Type: New Feature
Versions: 1.1
Reporter: simon godik
Secure vault gbean is a repository for sensitive data
[
http://issues.apache.org/jira/browse/GERONIMO-1259?page=comments#action_12362402
]
simon godik commented on GERONIMO-1259:
---
Deployment plans for an EAR are still readable, just unpack jar file with
deployment plans. For maven users, deployment
[ http://issues.apache.org/jira/browse/GERONIMO-1400?page=all ]
simon godik updated GERONIMO-1400:
--
Attachment: daytrader-jetty.patch
daytrader-tomcat.patch
patches for tomcat and jetty included
> modularize daytrader deployment p
Reporter: simon godik
Priority: Minor
use geronimo patch 1260 to modularize deployment plan
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more
[ http://issues.apache.org/jira/browse/GERONIMO-1260?page=all ]
simon godik updated GERONIMO-1260:
--
Attachment: geronimo-packaging-plugin-1260.patch
this patch enables element replacement in the deployment plan
to enable alt-dd processing set
Project: Geronimo
Type: New Feature
Components: deployment
Versions: 1.1
Reporter: simon godik
Priority: Minor
To simplify construction and maintainance of the combined deployment plan
create deployment plan template and preprocess it to create combined deployment
plan
://issues.apache.org/jira/browse/GERONIMO-1259
Project: Geronimo
Type: New Feature
Components: deployment
Versions: 1.1
Reporter: simon godik
Priority: Trivial
External plan is prefered method of deployment. For non trivial ear combined
deployment plan is difficult to manage
[ http://issues.apache.org/jira/browse/GERONIMO-1163?page=all ]
simon godik updated GERONIMO-1163:
--
Attachment: jmxexplorer.patch
jmxexplorer-img.jar
> improve jmx debug console
> -
>
> K
improve jmx debug console
-
Key: GERONIMO-1163
URL: http://issues.apache.org/jira/browse/GERONIMO-1163
Project: Geronimo
Type: Improvement
Versions: 1.0
Environment: all supported platforms
Reporter: simon godik
Attachments
22 matches
Mail list logo
