[
https://issues.jboss.org/browse/JBESB-2460?page=com.atlassian.jira.plugin...
]
Tom Cunningham resolved JBESB-2460.
-----------------------------------
Assignee: Tom Cunningham
Fix Version/s: 4.11
Resolution: Done
Make BinarySecurityToken an interface and make the implementation pluggable.
Adding a property to the security section of the jbossesb-properties.xml
containing your implementation class name makes it pluggable :
example :
<property
name="org.jboss.soa.esb.services.security.auth.ws.binarysecuritytoken.implementationClass"
value="org.jboss.soa.esb.services.security.auth.ws.BinarySecurityTokenImpl"
/>
BinarySecurityToken class hardwired to X.509 certificates
---------------------------------------------------------
Key: JBESB-2460
URL:
https://issues.jboss.org/browse/JBESB-2460
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Security
Affects Versions: 4.5
Reporter: Rune Molin
Assignee: Tom Cunningham
Fix For: 4.11
In order to support WS Security Kerberos Token Profile at a later time, please make the
class org.jboss.soa.esb.services.security.auth.ws.BinarySecurityToken abstract. Currently
it is hardwired to only support X.509 Certificate Token Profile.
By making this class abstract sooner rather than later, users could implement Kerberos
Token Profile themselves, without having to duplicate too much code. This will of course
mean moving the existing certificate bound implementation into a new class,
CertificateSecurityToken perhaps
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira