It didn't make any difference whether the authenticating user was a System
i user profile or one of your own users in your own database. If there was
a process that involved uniquely identifying a user and passing a userid and
password, it was "authenticating" and was using a User Entitlement that
would have to be paid for.

No possible way they can enforce this. I am guessing they meant to say
something else.

Aaron Bartell

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
Sent: Wednesday, April 11, 2007 11:11 AM
To: Midrange Systems Technical Discussion
Subject: Re: IBM will announce two new System i models, 515 and 525 on Apr.
10.

Nathan,

In the presentation I sat through, "authentication" was a generic term.
It didn't make any difference whether the authenticating user was a System i
user profile or one of your own users in your own database. If there was a
process that involved uniquely identifying a user and passing a userid and
password, it was "authenticating" and was using a User Entitlement that
would have to be paid for.

User Entitlements are unique users, not concurrent, and it is "use and
burn". There was some talk about deleting a user and creating a new one and
that would "restore" a UE, but counting users will be something I think IBM
will refine over time. Basically they said that now it is "self
enforcement". Even the OS will continue to run if you exceed the 40 max
users on a 515.

Should be an interesting area to watch. My guess is that the most simple
way to handle it will be to buy the External Access license and be done with
it.

Pete


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.