Hi,
thanks for the help, Kumar. As far as I can see this <as-context> is
restricted to a single EJB, and it's not an app-client wide
configuration. Does that even make sense, to have groups of EJB's with
different authentication method? (probably only if you have multiple
app-clients using those subsets, am I right?)
Also based on the doc you posted (thanks again) ejb->ejb-name should be
the same as in ejb-jar.xml, but I don't even have any EJB's declared
there. Isn't there a way to set this globally for all of the remote beans?
Thanks again
Regards,
Peter
2010-09-07 13:52 keltezéssel, glassfish_at_javadesktop.org írta:
> The <as-context> element under ior-security-config (sun-ejb-jar.xml) can specify a realm. If that realm is specified then that is the realm which will be used for authentication on the server (it will override any realm that was specified during client side programmatic login)
>
> http://docs.sun.com/app/docs/doc/820-4502/beaqw?l=en&a=view
>
> But when you do not have a realm specified then GlassFish tries to use the realm that was specified as part of ProgrammaticLogin. If No realm was specified for ProgrammaticLogin on the client side then the default realm is used.
>
> public java.lang.Boolean login(String user, String password,
> String realm, boolean errors) throws java.lang.Exception
>
> http://docs.sun.com/app/docs/doc/819-4721/beacp?l=en&a=view
>
> hope this clarifies.
> [Message sent by forum member 'kumarjayanti']
>
> http://forums.java.net/jive/thread.jspa?messageID=482024