I have not found a way to override those in the docs. Assuming that they
can be overridden, that would solve problem #1. I still don't know a way to
solve problem #2 through.
Theoretically, should this work?
<<client>>
InitialContext ctx = new InitialContext();
ctx.addToEnvironment(ctx.SECURITY_PRINCIPAL, "NEW_USER_ID");
<<EJB Bean>>
String userFromEnv =
sessionContext.getEnvironment().getProperty(InitialContext.SECURITY_PRINCIPA
L);
It makes sense that this should work, but the properties object
returned by getEnvironment() is always empty.
-----Original Message-----
From: Christian Sell [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 10, 2001 3:15 AM
To: Orion-Interest
Subject: Re: How to provide own security mechinism
Therese the UserManager and RoleManager classes that you can use resp.
provide your own replacement for. They are described in the docs that come
with orion.
----- Original Message -----
From: "John Pletka" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Tuesday, January 09, 2001 10:12 PM
Subject: How to provide own security mechinism
> Is it possible to override Orion's security classes with my own? The main
> things I'm looking for are 1) the ability to authenticate against a 3rd
> party LDAP server, and 2) From the client process, dynamically change the
> Principal reported in an EJBContext object.
>
