[ 
https://issues.apache.org/jira/browse/RAMPART-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18146490#comment-18146490
 ] 

Robert Lazarski edited comment on RAMPART-397 at 11/18/26, 12:27 AM:
---------------------------------------------------------------------

  Fixed on master in 6bd40bbd. The token dispatcher now loads issuers, 
validators, renewers and cancelers with the STS
  service's class loader, so a custom issuer can be packaged inside the service 
archive. The STS documentation page was
  corrected: nothing has to be removed from the modules directory, a custom STS 
simply does not engage the rahas module. Will
  ship in 2.0.0.



was (Author: robertlazarski):
  Fixed on master in 6bd40bbd. The token dispatcher now loads issuers, 
validators, renewers and cancelers with the STS
  service's class loader, so a custom issuer can be packaged inside the service 
archive. The STS documentation page was
  corrected: nothing has to be removed from the modules directory, a custom STS 
simply does not engage the rahas module. Will
  ship in 2.0.0.

  Three commits are waiting on local Rampart master, 201d23f9 for RAMPART-421, 
d2b312de for RAMPART-419 and 6bd40bbd for
  RAMPART-397. Push with git push origin master as robertlazarski.



> 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
>            Assignee: Robert Lazarski
>            Priority: Major
>             Fix For: 2.0.0
>
>
> 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 was sent by Atlassian Jira
(v10.3.26#10030026)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to