How to access LoginModule from EJB?

Question

Hello,
I have developed a custom login module and deploying my EJB by defining to use this custom login module.
Here is what I defined in orion-application.xml
   <jazn-loginconfig>
      <application>
         <name>CVTApplication</name>
            <login-modules>
               <login-module>
                  <class>cvt.security.SampleLoginModule</class>
                  <control-flag>required</control-flag>
                  <options>
                     <option>
                        <name>debug</name>
                        <value>true</value>
                     </option>
                  </options>
               </login-module>
            </login-modules>
      </application>
   </jazn-loginconfig>
...How can I call any of the methods that are defined in the custom login module within my EJB? How can I access to the custom login module class from EJB?
Thanks,
Mustafa

Answer 1

Simon McQueen <[email protected]> writes:
Then presumably to use SSL you would do
NameService=iioploc://localhost:7002/NameService (assuming default ports) ?Since we don't support CSIv2 as yet I don't think SSL will work with a
C++ orb client. I forget how we specify SSL in a java client for IIOP,
but yes I think its through the connection rather than some iiops URL.
The INS stuff isn't supported by the 1.3 Sun SDK CosNaming stuff tho'. Only IOR,
iiop and iiopname as PROVIDER_URL values can be used with
com.sun.jndi.cosnaming.CNCtxFactory for bootstrapping the Sun ORB as far as IRight, and even those generate an old-style INIT bootstrap
request. The 1.3 stuff is very old and incorrect, I haven't checked
whether 1.4 supports corbaloc, it certainly supports GIOP 1.2.
But even so we still support those kind of requests, they key is that
they are interoperable - you can use the same URL between restarts of
the server, with host2ior you cannot.
know. I think the WLS RMI/iiop docs and examples still recommend using this forUnfortunately the RMI-IIOP doc rewrite hasn't happened as yet. We
continue to support the JDK context (because supporting a pure JDK
client is a worthy goal for customers who want thin clients) but you
will get superior results using WLInitialContextFactory and an
appropriate IIOP URL (including corbaloc support and security in
SP1). In addition you should never use the Sun context factory on a
server, that will case the JDK Orb to be used instead of our RMI-IIOP
runtime.
client access (?). Clients will still have to use host2iior to get the two IOR s
if they want to do SSL I suppose. Or is it possible to do iiop://localhost:7002
?I will check.
andy