Brian Reinhold created RAMPART-397:
--------------------------------------
Summary: Custom STS cannot load custom issuer
Key: RAMPART-397
URL: https://issues.apache.org/jira/browse/RAMPART-397
Project: Rampart
Issue Type: Bug
Components: rampart-trust
Affects Versions: 1.6.2
Environment: Windows7 32 & 64 Tomcat 28 and 30 Axis2/Rampart deployment
Reporter: Brian Reinhold
A: Description of Problem
When creating a custom STS service as instructed by the documentation at
the site:
http://axis.apache.org/axis2/java/rampart/setting-up-sts.html
and invoking the service, a 'class not found' exception is thrown.
Therefore the token dispatcher cannot
call the issue() method of the custom token issuer.
B: Tests:
If one performs all the tasks above and replaces the custom token issuer
with the default rahas token
issuer, the default issuer is successfully loaded.
C: Addtional information:
The documentation states to remove the rampart module. Those instructions
are clearly in error. It is
assumed that the module to removed is the rahas.mar module.
D: Workaround:
The approach I am taking requires the Rahas/Rampart source distribution. In
this case I implement my
custom token issuer in the same impl package as the default token issuer.
Then I modify the rahas.mar
file to point to my custom issuer. In my case I am writing an issuer for a
SAML20 token so I replaced
that issuer. The new class file needs to be added to the rahas-1.6.2.jar in
the axis2/webapps/lib directory.
E: Remark:
There is probably a simple step missing from the documentation preventing
me from implementing the
custom issuer as intended. I also noted callbacks in the source code but I
could not find any
documentation on how to use them; though they may not be intended for
applications.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
