[JBoss ESB Development] - BaseCertLoginModule Does Not Work?
by h.wolffenbuttel
I changed the org.jboss.soa.esb.services.security.auth.login.CertificateLoginModule to org.jboss.security.auth.spi.BaseCertLoginModule just to see if i can get the authentication working.
I have placed the following application-policy in login-config.xml:
| <application-policy name = "CertLogin">
| <authentication>
| <login-module code="org.jboss.security.auth.spi.BaseCertLoginModule"
| flag = "required">
| <module-option name="password-stacking">false</module-option>
| <module-option name="securityDomain">java:/jaas/CertLogin</module-option>
| <module-option name="verifier">org.jboss.security.auth.certs.AnyCertVerifier</module-option>
| </login-module>
| <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule"
| flag = "required">
| <module-option name="password-stacking">false</module-option>
| <module-option name="usersProperties">props/certlogin-users.properties</module-option>
| <module-option name="rolesProperties">props/certlogin-roles.properties</module-option>
| </login-module>
| </authentication>
| </application-policy>
|
When authentication takes place a few things go wrong:
- The name of the Certificate Should be the value of CN but it's the complete dname value => "CN=test, OU=test, O=test, L=test, ST=test, C=NL".
- If do not declare a org.jboss.security.auth.certs.AnyCertVerifier (always true) for my Certificate validation, the validation uses the dname as an alias to get a Certificate from my Truststore. Because an alias is not the same as a dname this never returns a Certificate from my Truststore. So my Certificate is never valid this way.
Am I using the classes the wrong way? Or is this the same issue as the problem with the org.jboss.soa.esb.services.security.auth.login.CertificateLoginModule?
Regards,
Hans
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4259357#4259357
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4259357
16 years, 6 months
[jBPM Development] - Extending HistorySession
by tcr
Hi,
some time ago I asked in the user forum about experiences extending the history-session.
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=161482
To me it seems that there are some public getters missing so that you can actually extend the historysession. In addition the binding for the HistorySessionChain is missing.
Is there a way that you could add public getters for the members of the history events in the next release?
Otherwise it is really hard and ugly to implement a custom history (e.g. to send customer specific audit-data to a backend system)
What I mean are getters like....
Event: ActivityEnd, DecisionEnd
Public getter for: transitionName
Event: TaskActivityStart, TaskAssign, TaskCreated, TaskDelete, TaskUpdated
Public getter for: task
Event: TaskAssign
Public getter for: assignee
Event: TaskComplete
Public getter for: outcome
Event: TaskDelete
Public getter for: reason
Event: VariableCreate, VariableUpdate
Public getter for: variable
etc...
That would be really great because we could use jBPM poperly :-)
Regards
Torsten
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4259306#4259306
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4259306
16 years, 6 months