By no additional charge, I meant that DIRMAINT or any product that
would need to do authentication would not have to have a charge for
having an ESM do the authentication.
Jim
Alan Altmark wrote:
On Tuesday, 12/11/2007 at 04:05 EST, Jim Bohnsack [EMAIL PROTECTED]
wrote:
B) There
On Tuesday, 12/11/2007 at 04:05 EST, Jim Bohnsack [EMAIL PROTECTED]
wrote:
B) There should be no additional charge. Not having to maintain
separate authorization paradigms in each product just about has be less
expensive for the vendor. Certainly there would be an initial startup
cost, but
On Tuesday, 12/11/2007 at 08:45 EST, David Boyes [EMAIL PROTECTED]
wrote:
This was where I was going a few months ago with the idea of integrating
RACF into the base VM.
Even given the general awfulness of RACF, at that
point IBM would have a basic level of function to depend on, and you
: DIRMAINT authentication
John,
I agree that security/authentication is pretty much an afterthought in
DIRMAINT but I doubt IBM would be interested in a rewrite just because
it is a PITA. I am not very familiar with VM-Secure how do they handle
security issues?
Perhaps if the compitition for buisness
On Tuesday, 12/11/2007 at 09:28 EST, Jim Bohnsack [EMAIL PROTECTED]
wrote:
What you do all think or am I the only one who thinks that this is a
problem in DIRMAINT or an opportunity for improvement?
To be clear, you're talking about *authorization*, not *authentication*.
As of z/VM 5.3, I
Subject: Re: DIRMAINT authentication
On Tuesday, 12/11/2007 at 09:28 EST, Jim Bohnsack [EMAIL PROTECTED]
wrote:
What you do all think or am I the only one who thinks that this is a
problem in DIRMAINT or an opportunity for improvement?
To be clear, you're talking about *authorization
Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
Behalf Of Alan Altmark
Sent: Tuesday, December 11, 2007 1:01 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: DIRMAINT authentication
On Tuesday, 12/11/2007 at 09:28 EST, Jim Bohnsack [EMAIL PROTECTED]
wrote:
What you do all
A) There would be some learning curve involved in implementing it but
you would only have to learn the basics of it once.
B) There should be no additional charge. Not having to maintain
separate authorization paradigms in each product just about has be
less
expensive for the vendor.
