Client eDir caching (When?)
Eric Young
caching, which would have been somewhat similar to Microsoft in that login
information and policies/etc would be cached if the network/server was down
temporarily. Whatever happened w/ this?
Tony Pedretti
I haven't heard anything about eDirectory, but I had a chance to speak with
some management types in Provo the past summer and I recall one of them
mentioning that one of the new features for the next version of ZENworks for
Desktops (ie. the 6.5 suite) is Group Policy caching.
--
Tony Pedretti
TransUnion LLC
Eric Young
Novell SecureLogin 3.5.
http://www.novell.com/collateral/4621348/4621348.html
What a cop-out... Microsoft doesn't require you to purchase an additional
client to be able to login with cached credentials, so why would Novell?
One of the best things about Active Directory is the minimal downtime to users
when AD is down, thanks to cached credentials. With eDirectory, sure, you can
replicate partitions all over the place, but if you have a single eDir server at
a site (like a WAN site), users are typically SOL if that eDir server goes down.
I'm not really a proponent of AD, but in this particular case I am.
Eric Young
Anyway, the GP caching for ZEN will be nice, but what we really need is Login
caching, similar to Windows domain logins, so that if eDir is down, the client
will login with cached credentials. That is what was supposedly going to be
added to the Novell client (local eDir caching).
"Tony Pedretti" <yno...@NOSPAMhotmail.com> wrote in message
news:3XiSb.3432$Wh....@prv-forum2.provo.novell.com...
Tony Pedretti
You'll probably get better results by submitting an enhancement request and
following up with people on these forums who may be interested as well...
http://support.novell.com/enhancement
I can see in some of our locations where this feature would be valuable. If
you submit a request and post back your Entry id of it, I'll make one as
well referencing yours.
I imagine it would take a whole new client and an eDirectory update for this
feature to be implemented. If you can get enough support from others and
let Novell know about it, good chance they'll give it a higher priority.
Eric Young
already a request for this, or that this was something that Novell planned to do
anyway (I believe it was originally planned for the 4.9 client). I can no
longer find this information on Novell's site, but it doesn't surprise me that
they would remove the information so as to steer customers toward purchasing
SecureLogin. As far as I know, there is no way of customers tracking
enhancement requests, or searching a database to see if an enhancement was
already requested.
Are you saying cached credentials isn't a secure feature? If so, it is quite
funny that this is a new feature of -Secure-Login.
As for eDirectory being secure/reliable, I sure as heck did not have any fun
patching all our servers for all the SSL/TLS ASN.1 decoder vulnerabililities :(
"Tony Pedretti" <yno...@NOSPAMhotmail.com> wrote in message
news:nqySb.4085$Wh....@prv-forum2.provo.novell.com...
Eric Young
servers after applying the vulnerability patches. All that had to occur was
stopping/restarting the eDir services (very nice!). Unfortunately we run mostly
Netware eDirectory servers, and eDir on Netware still requires "reset server"
reboots for such patches :(
Eric Young
RFE000000027672
Basically all I'm asking is that Novell takes back "credential caching" from
SecureLogin and puts it in the Novell client. That, or Novell should bundle
Securelogin free with eDirectory and the Novell client.
"Tony Pedretti" <yno...@NOSPAMhotmail.com> wrote in message
news:nqySb.4085$Wh....@prv-forum2.provo.novell.com...